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

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.

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.

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: 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.

Status

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

References

See the terminology that Microsoft uses to describe software updates.

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
Additional file information
Thuộc tính

ID Bài viết: 3090973 - Xem lại Lần cuối: 04-11-2015 - Bản sửa đổi: 1

Phản hồi