July 8, 2013 at 5:20 am
Hi
Rather a strange issue with multiple SQL server instances - SQL server abruptly not responding to client applications for a brief period (5-15 minutes), but it’s started responding as soon as these errors raised on SQL error log.
SQL version: 2008 R2 enterprise RTM
OS version: Windows server 2008 R2 Enterprise, Service pack1
Client applications (IIS7) displayed with error 8004e024 - COM+ unable to create the instance when this issue occurring.
Message
Error: 8510, Severity: 20, State: 1.
Message
Enlist operation failed: 0x8004d00e(failed to retrieve text for this error. Reason: 15100). SQL Server could not register with Microsoft Distributed Transaction
Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.
Message
Error: 8509, Severity: 16, State: 1.
Message
Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: 0x8004d00e(failed to retrieve text for this error. Reason: 15105).
Any idea what’s causing this issue? Any help on this highly appreciated.
Thanks
PS
July 9, 2013 at 8:43 am
Open control panel->administrator tools->Services-> find the MS DTS Service just run it.
July 9, 2013 at 8:50 am
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
July 10, 2013 at 4:11 am
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
July 25, 2013 at 1:10 am
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
November 15, 2013 at 3:33 am
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. .. 🙂
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply