Cannot create new connection because in manual or distributed

 · Cannot create new connection because in manual or distributed transaction mode. When executing this classic ASP code: On Error Resume Next www.doorway.rurans www.doorway.rue "EXEC sp_Name ",, adCmdText + adExecuteNoRecords www.doorway.rue "UPDATE table_name ",, adCmdText + adExecuteNoRecords If Err Then www.doorway.ruckTrans WriteError www.doorway.ru " " .  · OLE DB provider "SQLNCLI" for linked server "S1" returned message "Cannot create new connection because in manual or distributed transaction mode.". Msg , Level 16, .  · Answers. 1) Check the datasouce, ensure you are using SQL Server Native Client provider. 2) Check the source database, if you have enabled snapshot isolation on the DataSource – if yes; make sure to turn MARS on (Multiple Active Result Sets). Edit the datasource, set the property MARS Connection to be true.

Re:dbExpress MS SQL issue: Cannot create new connection because in manual or distributed transaction mode. Hello, Ignacio! You wrote to Ramesh Theivendran on Mon, We are now continually getting 'Cannot create new connection because in manual or distributed transaction mode' errors in code like that below: Code: Select all. begin if www.doorway.runt1 then begin with DataResource do begin www.doorway.ruransaction; try with MSDeleteCustomerNotes do begin ParamByName ('URNToDelete').AsString. Cannot create new connection because in manual or distributed transaction mode. This was getting thrown after an insert, and the problem was very non-obvious. I found one potential solution on Occasionally Useful Software's post about Ruby and SQL Server, but that seemed a little heavy-handed.

'Microsoft OLE DB Provider for SQL Server' Error: Cannot create new connection because in manual or distributed transaction mode. PS. Database settings from www.doorway.ru: # Database for this installation. Cannot create new connection because in manual or distributed transaction mode Suggested Work Around: Set "poFetchDetailsOnDemand" (for the Provider) to False. This is a known issue when it is set to True. \"Cannot create new transaction because capacity was exceeded.\" \"Cannot create new connection because in manual or distributed transaction mode.\" To resolve the errors, use one of the following workarounds: On the DataSetProvider Options property, make sure poFetchBlobsOnDemand and.