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

Back to the top

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:

Back to the top

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.

Back to the top

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.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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

   Date         Time   Version         Size       File name
   -----------------------------------------------------------
   06-Jun-2005  22:46  8.11.50523.0      239,104  Mssdi98.dll      
   12-Jul-2005  17:23  2000.80.2148.0    430,080  Pfclnt80.dll     
   08-Jul-2005  01:50  2000.80.2148.0    323,584  Sqlagent.exe     
   08-Jul-2005  02:51  2000.80.2148.0    118,784  Sqldiag.exe      
   08-Jul-2005  02:09  2000.80.2148.0    102,400  Sqlfth75.dll     
   08-Jul-2005  16:07  2000.80.2148.0  9,154,560  Sqlservr.exe  

SQL Server 2000 64-bit version

   Date         Time   Version         Size        File name     Platform
   ----------------------------------------------------------------------
   06-Jun-2005  22:46  8.11.50523.0       758,784  Mssdi98.dll   IA-64
   08-Jul-2005  16:22  2000.80.2148.0   1,187,840  Pfclnt80.dll  IA-64
   08-Jul-2005  17:10  2000.80.2148.0   1,061,376  Sqlagent.exe  IA-64
   08-Jul-2005  16:33  2000.80.2148.0     334,336  Sqldiag.exe   IA-64
   08-Jul-2005  16:24  2000.80.2148.0     246,784  Sqlfth75.dll  IA-64
   08-Jul-2005  22:14  2000.80.2148.0  24,935,424  Sqlservr.exe  IA-64

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

Back to the top

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.

Back to the top

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

Back to the top

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:

Back to the top