Transaction Scope - The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "XXX_LINKED_SERVER" was unable to begin a distributed transaction. OLE DB provider "SQLNCLI" for linked server "

Last post 07-18-2008 3:11 PM by mcook78. 1 replies.

Sort Posts:

  • Transaction Scope - The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "XXX_LINKED_SERVER" was unable to begin a distributed transaction. OLE DB provider "SQLNCLI" for linked server "

    05-15-2008, 12:43 PM
    • Member
      2 point Member
    • ankem
    • Member since 03-13-2008, 9:55 PM
    • Posts 8
    Hello, I've a problem with a software developed in C# with the framework 2.0. This is the error I receive : The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "XXX_LINKED_SERVER" was unable to begin a distributed transaction. OLE DB provider "SQLNCLI" for linked server "XXX_LINKED_SERVER" returned message "No transaction is active.". If I try directly to restart the process, it works fine. Is there someone who can help me ? This is the process 1. In C# --> Call of a Query : select from the linked server (db in sql 2005) and insert into a table SQL 2005 2. In the C# --> using (TransactionScope scope = new TransactionScope()) and insert in a table in SQL 2005 which is link server Thank in advance.
  • Re: Transaction Scope - The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "XXX_LINKED_SERVER" was unable to begin a distributed transaction. OLE DB provider "SQLNCLI" for linked server &q

    07-18-2008, 3:11 PM
    • Member
      2 point Member
    • mcook78
    • Member since 07-18-2008, 2:48 PM
    • Posts 1

    I was about to ask you if you ever figured this out because I'm having the same problem today.  Thankfully my genious architect friend turned me on to connection pooling and sure enough that was my problem.  I turned connection pooling off "Pooling=false" in the connection string and now everything works.  I suppose another option would be to use a separate connection string.

     Matt

Page 1 of 1 (2 items)