Post reply

SQL2k MSDTC Problem

  • April 12, 2004 at 1:03 pm

    #179169

    Hi,

    I recently moved & upgraded a database from 7.0 to 2000 that makes use of linked servers. After upgrading, a number of queries started failing with the error below. These linked servers with this problem either had a stopped MSDTC or were behind a firewall. I've read the articles on how to configure MSDTC to work through a firewall, but before I do this I'm wondering why this is even happening. There were no problems when the database was at SQL 7.0. Does anyone know why sql 2000 would need to use MSDTC, but SQL7.0 would not? I don't need to use a distributed transaction, so ideally I'd like to somehow tell SQL not to use MSDTC at all. Any ideas?

    Thanks

    Server: Msg 7391, Level 16, State 1, Line 1

    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].

    Charlie Pyne

  • April 15, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • April 15, 2004 at 8:56 am

    #502962

    You can try Microsoft Knowledge base articles 306212(Troubleshooting linked server error 7391) and 817064(Enable network dtc access in windows server 2003). We had success in fixing the Error 7391 yesterday. Good Luck.

     

    Srinath Potlapalli.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply