Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
emundorf
Starting Member
15 Posts |
 Posted - 2007-02-09 : 12:25:36
|
| I'm trying to connect to another slq server db through a linked server (and synonyms) but I get the following error.Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. ,Unable to start a nested transaction for OLE DB provider "SQLNCLI" for linked server "BURT". A nested transaction was required because the XACT_ABORT option was set to OFF. , at Westfalia.TDMN.TxObjects.TxBurtOCIInterface.BurtOCIPalletChangedRecords_Get() , --- End of inner exception stack I've set up MSDTC and executed the procedures noted in MS's article ID 873160. I am using 2005, but the Burt server is 2000. I can run the stored procedure from my server, which queries theirs. But when I execute the sp from a service, I get the error. Any help would be greatly appreciated. |
|
|
emundorf
Starting Member
15 Posts |
Posted - 2007-02-09 : 13:25:02
|
| The problem is directly related to an update statement (from within a stored procedure) to a table within the linked server. The update is within a cursor. But the calling routine from a C# assembly using a transaction model. From within the method on the assembly, we do a BeginTransaction/CommitTransaction. I belive that if I add in a BEGIN/COMMIT around the update in the stored procedure, it should work, but our transactional model doesn't like this... |
 |
|
|
|
|
|
Linked Server from 2005 to 2000 Trans failure