Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Reenlist can't be called when SQL Server receives transaction outcome from MSDTC in Windows Server 2012 R2

Reenlist can't be called when SQL Server receives transaction outcome from MSDTC in Windows Server 2012 R2

View products that this article applies to.

This article describes a conflict between Microsoft SQL Server and Microsoft Distributed Transaction Coordinator service (MSDTC) in Windows Server 2012 R2. A hotfix is available to fix this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

Consider the following scenario:
  • You're using SQL Server in combination with MSDTC.
  • You creates a distributed transaction that spans two or more database instances.
  • During two-phase commit, SQL Server prepares the transaction, but its database has to restart.
  • As part of the database restart, SQL Server will try to recover its log, and will have to communicate with MSDTC for outcome by calling Reenlist.
In this scenario, when SQL Server calls Reenlist during the database recovery, the MSDTC proxy throws an error message XACT_E_RECOVERYALREADYDONE (0x8004D104L) that indicates Reenlist is no longer available to be called.

↑ Back to the top

Resolution

To fix this issue, we have released a hotfix. Even though this issue is observed only in Windows Server 2012 R2, the hotfix also applies to Windows 8.1 and Windows RT 8.1.

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2
Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes aren't listed, are signed with a Microsoft digital signature.
x86 Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Msdtcprx.dll2001.12.10530.18034720,89620-Aug-201517:20x86
Xolehlp.dll2001.12.10530.1803450,68820-Aug-201517:34x86
x64 Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Msdtcprx.dll2001.12.10530.18034871,42420-Aug-201517:24x64
Xolehlp.dll2001.12.10530.1741561,44029-Oct-201401:16x64
Msdtcprx.dll2001.12.10530.18034720,89620-Aug-201517:20x86
Xolehlp.dll2001.12.10530.1803450,68820-Aug-201517:34x86
Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Msdtcprx.dll2001.12.10530.18034642,04820-Aug-201517:06Not applicable
Xolehlp.dll2001.12.10530.1638451,71222-Aug-201302:10Not applicable
Additional file information
x86 Windows 8.1
File propertyValue
File nameUpdate.mum
File versionNot applicable
File size1,784
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable
File nameX86_371607d1b28380f8ea27e02daaea0c72_31bf3856ad364e35_6.3.9600.18034_none_6f40ce842bc8ceb1.manifest
File versionNot applicable
File size702
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable
File nameX86_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.3.9600.18034_none_e1c88e97d4bf0dfd.manifest
File versionNot applicable
File size6,520
Date (UTC)20-Aug-2015
Time (UTC)19:51
PlatformNot applicable
x64 Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_6a7ed12e076afa4086d7c90226660b88_31bf3856ad364e35_6.3.9600.18034_none_1432988083f73ea8.manifest
File versionNot applicable
File size706
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable
File nameAmd64_bda90ef8cbf10a53fc08bccd85da6f29_31bf3856ad364e35_6.3.9600.18034_none_6376f31f89e655c3.manifest
File versionNot applicable
File size706
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable
File nameAmd64_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.3.9600.18034_none_3de72a1b8d1c7f33.manifest
File versionNot applicable
File size6,525
Date (UTC)21-Aug-2015
Time (UTC)10:33
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,896
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable
File nameWow64_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.3.9600.18034_none_483bd46dc17d412e.manifest
File versionNot applicable
File size6,240
Date (UTC)20-Aug-2015
Time (UTC)19:51
PlatformNot applicable
Windows RT 8.1
File propertyValue
File nameArm_1eeffb75132b79c966d9c0abcd47047b_31bf3856ad364e35_6.3.9600.18034_none_efd176d820dbb986.manifest
File versionNot applicable
File size702
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable
File nameArm_microsoft-windows-com-dtc-client_31bf3856ad364e35_6.3.9600.18034_none_e1cb00efd4bc2cc3.manifest
File versionNot applicable
File size6,523
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,566
Date (UTC)21-Aug-2015
Time (UTC)10:26
PlatformNot applicable

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbfix, kbautohotfix, kbhotfixserver, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3090973
Revision : 1
Created on : 1/7/2017
Published on : 11/4/2015
Exists online : False
Views : 185