Distributed Transaction on Windows 2000 Professional

Just curious if anyone out there has had success running a Distributed Transaction on Windows 2000 Professional SP4 lately?

I have come to the conclusion that is is virutally impossible. I am running MSDE on a Win2k Pro machine and trying to run a distributed transaction via linked server and am getting the
"The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction."
error. Yes I have been scouring the web looking for answers and have implemented pretty much everything I have run accross... and Yes the MSDTC service is started on both machines... BTW: If I run the procedure on XP it works great!!!

I am wondering if anyone even uses Win2k Pro anymore let alone trying to run a distributed tarnsaction on the darn thing.

If anyone out there has it running let me know I would love to chat with you for a minute or two.

The server you are connecting to can it see you machine by name. I know previously that the destination server tries to make the connection back to the source server to complete the distributed connection. If you have a firewall or its on a different network/domain it can often be the case that the destination can't get back to the source.

On the destination ping your server and also try and connect by name \\servername. What happens if either of these fail this could be your problem. In which case a hack solution is to put an entry in the hosts file of the target server (if its not a firewall issue)

|||

Thanks for the reply!

The machines can "see" each other. I downloaded and ran the dtcping.exe utility and it ran with no errors. I also placed entries in the hosts files on both server and client as well.

I am thinking it has something to do with SP4. I ran across this article

http://support.microsoft.com/kb/908620

and it mentions modifying some registry entires but I looked in my registry and they were not there. I backed up the registry and made the entries but that did not seem to fix the error either.

I'm stumped.