I am trying to move an application that is currently using SQL2000 to SQL2005
Production environment:
Server1: Win 2000/SQL2000
Server2: Win 2003/IIS/COM+ & ASP
Trying to move to:
Server1: Win 2003/SQL2005
Server2: Win 2003/IIS/COM+ & ASP
The problem is that when a COM+ control tries to start up a transaction I keep getting the following error: error '8004d00a': New transaction cannot enlist in the specified transaction coordinator
I have discovered a ton of articles, blogs, etc. that suggest setting up security in component services, the firewall, testing with DTCPing (which works fine) and more but it seems that they were all talking about Win2003 and SQL2000. I cannot find anything that specifically references SQL2005.
I have modified both servers with all of the suggestions including the firewall (which is turned off BTW) but to no avail.
Has anyone run into this problem with SQL2005 and hopefully solved it?
Thanks,
Mark
I'm having the same problem... no resolution yet.
Using profiler I can tell that DTC is reaching SQL.
|||I actually figured out the problem (in my case). I was working within a test environment using 2 Virtual Servers. The problem was that the two servers were copied from the same base server image (without being sysprep'd) so they had identical identifiers throughout the system. When I created a brand new server and hooked everything up and followed all of the recommended setups it started working. My problem had nothing to do with SQL200 vs SQL2005.
The big clue came when I ran the DCOM "ping" app. It said that communication was working but the DCOM ID's were identical and that may cause a problem - and it did.
Good luck.
No comments:
Post a Comment