MSDTC inconsistiently fails. help!!!!

  • Hi,

    I have several SQL Servers currently running SQL Server 2000 sp4 on Windows

    2003 server sp1. I constantly keep stumbling across the following error "The

    operation could not be performed because the OLE DB provider 'SQLOLEDB' was

    unable to begin a distributed transaction".

    What makes this error problematic is that it is inconsistient, sometimes it

    works and sometimes it doesnt. However, either way, the error is cropping up

    enough times to hinder operations.

    I have read many posts suggesting that it is the MSDTC security settings

    (which I have checked, I have the settings correct)

    Other posts sugest that the DTCtrace log is too small, however concurrent

    active connections to these servers is not high enough to require a bigger

    file.

    The servers can be pinged, any firewall issues have been checked,

    @@servername all correctly match, I have also used the setting 'SET

    XACT_ABORT ON' before executing the failing code.

    On the same platform I have not encountered any issues with Windows server

    2000 or windows 2003 server pre sp1.

    Is this an issue with sp1 on windows 2003 server???? Any ideas would be

    gratefully accepted.

  • Not sure this is the same issue I have ever met.

    Did you checked the checkbox to install SQL Server SP4 recently? If you forgot to checked the checkbox, the installation can completed but the connection issue exists.

    You can try to uninstall SQL Server SP4 and reinstall it to fix the issue.

  • which checkbox is this? As far as I know the SQL Server SP4 is installed correctly. Plus, to uninstall SP 4 is a complete uninstall of SQL server. This seems a little drastic, I feel it is more a bug with the operating system than the SQL Server

  • Were these servers imaged? Perhaps something like Ghost? I had this problem before because the distributed transaction coordinator saw all the boxes as the 'same' one, even though they had different IP and computer names. I will look around for the solution I got from Microsoft.

    Here is where I posted Microsoft's diagnosis:

    http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=10382#bm55522



    Michelle

  • Thanks for your reply, although the servers arent imaged. They are just normal SQL Servers. I ran a query 3 times this morning, it finally worked on the last execution.

Viewing 5 posts - 1 through 4 (of 4 total)

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