MSDTC errors - SQL server stopped responding to any request

Question

MSDTC errors - SQL server stopped responding to any request

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

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

ssabir SSC Rookie Points: 35 More actions · Answer 1

Open control panel->administrator tools->Services-> find the MS DTS Service just run it.

EdVassie SSC Guru Points: 60540 More actions · Answer 2

How did your Windows instances get created? Did someone do a Windows install, a Sysprep type install, or simply clone an existing system.

If your system was cloned from a master build, then all systems cloned from this build will have the same CID GUID value for MSDTC, which can cause problems.

If you suspect this might have happened, google 'change msdtc cid' for details on how to apply a new CID value to MSDTC, it only takes about 5 minutes to do.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

Sam_1234 Old Hand Points: 338 More actions · Answer 3

Thanks ssabir and EdVassie for your reply.

EdVassie,

Windows instances were created by clone. It’s actually 5 nodes cluster with 4 SQL instances and a clustered MSDTC. All of them have got same GUIDs for MSDTC, MSDTCUIS, MSDTCTIPGW & MSDTCXATM (under CID) for all 5 nodes.

I’ll change them and see if it helps. Many thanks for your help.

Regards,

PS

cmunch SSC Enthusiast Points: 138 More actions · Answer 4

Hi,

So, was that the answer to your question? Because I'm currently involved with a SQL 2008 R2 installation where we see massive amounts of DTC errors like yours..

Brg,

Claus

cmunch SSC Enthusiast Points: 138 More actions · Answer 5

Hey guys,

Just wanted to update you on my "findings" in our issue.

I bumped into this MSDN page, where I could find the errorcode that SQL dropped in the log.

http://msdn.microsoft.com/en-us/library/cc231196.aspx

On there, there is a .pdf document, where this description is:

"0x8004D00E XACT_E_NOTRANSACTION": The transaction has already been implicitly or explicitly committed or aborted.

From there, I enabled the traceflag 1222 and saw that on the exact moment, there was a huge amount of deadlocks.

Just my 2 cents. .. 🙂