FIX: An access violation may occur when a deadlock graph is written to the error log in SQL Server 2000

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Information about whether you must restart the computer after you install the hotfix package
• Information about whether the hotfix package is replaced by any other hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

Consider the following scenario:

• You enable the 1204 trace flag in Microsoft SQL Server 2000 to identify SQL Server deadlock events.
• A deadlock event occurs, and a deadlock graph is automatically written to the SQL Server error log.

In this scenario, SQL Server may generate an access violation under rare circumstances. Additionally, an access violation may occur in SQL Server when the deadlock graph is written to the error log.

For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

This problem occurs because of a rare timing-related condition. You may experience this condition if a deadlock occurs. An access violation occurs if a Microsoft Distributed Transaction Coordinator (MSDTC) transaction is orphaned after a deadlock is detected but before that deadlock graph is written to the error log.

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

• The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.
  
  Note This issue does not occur on systems that use the Intel Itanium processor architecture.
• The system is running a 64-bit version of the Microsoft Windows Server operating system.
• The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information

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 this specific problem.

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, submit a request to 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 Web site: 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.

Prerequisites

You must have SQL Server 2000 SP4 installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix. However, SQL Server 2000 automatically restarts when you apply this hotfix.

Registry information

You do not have to change the registry when you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the problems that this article describes. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000 32-bit versions

SQL Server 2000 64-bit version

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

To work around this problem, disable the 1204 trace flag in SQL Server. For more information about how to enable or disable tracing in SQL Server 2000, see SQL Server Books Online.

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

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base: For more information about how to troubleshoot a deadlock in SQL Server 2000, click the following article number to view the article in the Microsoft Knowledge Base: