March 31, 2015 at 2:06 pm
We have a rather large environment and have just a couple of boxes out there that we are getting cannot begin distributed transaction on inserts and updates but works fine on selects. Inserts and updates work fine outside the begin tran / commit so it's definitely DTC
We have checked the configuration on and the source box is set to No authentication required same for destination.
We have: Verified credentials running the service, changed them, same problem. Uninstalled and re-installed MSDTC per Microsoft instructions.
Have run all the tools for checking DTC DTCPing etc and followed those procedures which typically in the past has resolved any DTC issues. Other than swapping out the offending pc for a new one we are at a loss
Any ideas will be given virtual free donuts 😀
April 1, 2015 at 4:49 pm
SUCCESS 🙂
The offender was on an XP box. The situation was Windows 2008 / SQL 2008 had a linked server to an XP box / MDSE 2000.
The DTC transactions were being run on the Win2k8/SQL2k8. The WinXP/MSDE2k was where the custom entry was located as described below. Hope that clarifies.
It was a custom entry in the host file
C:\Windows\System32\drivers\etc\hosts\
That was pointing to a retired server
What a hair puller
April 1, 2015 at 11:00 pm
Frankie-464050 (4/1/2015)
SUCCESS 🙂The offender was on an XP box
It was a custom entry in the host file
C:\Windows\System32\drivers\etc\hosts\
That was pointing to a retired server
What a hair puller
I would rephrase that to "the offender is the one that has an Windows XP box in the role of..."
😎
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply