SQL Server Performance

Distributed transaction error on linked servers

Discussion in 'Performance Tuning for DBAs' started by pforbord, Apr 19, 2005.

  1. pforbord New Member

    Please help... I've found the post http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=3451 and have followed the steps there to attempt to resolve this issue with no success. In a nut shell, we have two servers both running SQL Server 2000. One box is running Server 2000 and the other 2003. I can select data, but when attempting an update I get the following error:

    Server: Msg 7391, Level 16, State 1, Line 7
    The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
    [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
    OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].


    Error with DBCC TraceON.......................................

    DBCC TRACEon (3604, 7300)

    OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IRowset::GatherStats returned 0x80004005: OLE DB provider SQLOLEDB returned 0x80004005 for OpenRowset during statistics gathering].
    OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IRowset::GatherStats returned 0x80004005: OLE DB provider SQLOLEDB returned 0x80004005 for OpenRowset during statistics gathering].
    OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IRowset::GatherStats returned 0x80004005: OLE DB provider SQLOLEDB returned 0x80004005 for OpenRowset during statistics gathering].
    DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    Server: Msg 7391, Level 16, State 1, Line 7
    The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
    [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
    OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].

    Any help would be greatly appreciated. Thanks.
  2. satya Moderator

    Have you checked whether MSDTC is started on both the machines?

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. deepakontheweb New Member

Share This Page