The Microsoft Distributed Transaction Coordinator (MSDTC) service may stop unexpectedly on a computer that is running Windows Server 2012 or Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, one of the following events is logged in the Application log:
Log Name: Application Source: Microsoft-Windows-MSDTC Event ID: 4441 Task Category: SVC Level: Error Keywords: Classic User: N/A Description: A MS DTC component has encountered an internal error. The process is being terminated. Error Specifics: CImpITransactionTrackerFactory::Create (d:\w7rtm\com\complus\dtc\dtc\dtcuis\src\uisimp.cpp@693): CImpITransactionTrackerFactory::Create, pLink is expected to be non NULL here
Log Name: Application Source: Microsoft-Windows-MSDTC Event ID: 4441 Task Category: SVC Level: Error Keywords: Classic User: N/A Description: A MS DTC component has encountered an internal error. The process is being terminated. Error Specifics: Expecting pLink->m_fQueued to be FALSE
This issue occurs because an internal structure is not handled correctly.
To resolve this issue in Windows Server 2012, install update rollup 2984005.
To resolve this issue in Windows Server 2008 R2 SP1, install the hotfix that is described in the "Hotfix information" section.
For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2984005 September 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must be running Windows Server 2008 R2 SP1.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To apply this hotfix, you do not have to make any changes to the registry.
You must restart the Distributed Transaction Coordinator (MSDTC) service after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Windows Server 2008 R2
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
To work around the issue, create a DWORD registry value by using the name "NoTracking" together with a value of 1 under the HKLM\Software\Microsoft\MSDTC registry key. Then, restart the MSDTC service.
Note If you use the workaround to work around this issue, the information for transactions that are distributed is not displayed in the user interface (UI) of the Component Services application. Therefore, transactions that are assigned the "indoubt" status cannot be resolved. These transaction may then cause locking problems on the database servers on which the transactions are distributed.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2