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.
•	Whether you must restart your computer after you install the hotfix package.
•	Whether the hotfix package is replaced by any other hotfix package.
•	Whether you must make any registry changes.
•	The files that are contained in the hotfix package.

Back to the top

When you use a client application such as SQL Query Analyzer to start or to enlist into a distributed transaction after you have installed Microsoft SQL Server 2000 Service Pack 4 (SP4), you receive an error message that is similar to the following:Additionally, if you run a trace session by using SQL Profiler, you receive an error message in the trace window that is similar to the following:Note The 8526 error occurs when you implicitly or explicitly use the SAVE TRANSACTION statement to start or to enlist into a distributed transaction and the server severs the connection with the client application.

Back to the top

This problem occurs because the SAVE TRANSACTION statement in SQL Query Analyzer is not supported in distributed transactions that are either started with the BEGIN DISTRIBUTED TRANSACTION statement or that are escalated from a local transaction.

Note In SQL Server 2000 SP1, the undocumented trace flag 8599 was added to enable some applications to bypass the test for backward compatibility and also to make upgrading SQL Server 2000 easier. Additionally, an incorrect behavior that enabled the savepoint in a distributed transaction that did not have a trace flag was fixed in SQL Server 2000 SP4. As a result, SQL Server 2000 SP4 client applications may experience the problem that is mentioned in the Symptoms section, whereas other versions of SQL Server 2000 will not be affected.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

•	Microsoft SQL Server 2000 Service Pack 4 (SP4) For information about how to obtain SQL Server 2000 SP4, see the following article in the Microsoft Knowledge Base: 290211 (http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack

Restart information

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

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. 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
   28-Jul-2005  15:25  2000.80.2151.0    290,816  Ntwdblib.dll
   28-Jul-2005  15:25  2000.80.2151.0    430,080  Pfclnt80.dll
   28-Jul-2005  01:57  2000.80.2151.0    323,584  Sqlagent.exe
   28-Jul-2005  03:01  2000.80.2151.0    118,784  Sqldiag.exe
   28-Jul-2005  02:06  2000.80.2151.0    102,400  Sqlfth75.dll
   28-Jul-2005  03:59  2000.80.2151.0  9,154,560  Sqlservr.exe
   28-Jul-2005  15:25  2000.80.2151.0    176,128  Stardds.dll
   28-Jul-2005  15:25  2000.80.2151.0     35,328  Ums.dll

SQL Server 2000 64-bit version

   Date         Time   Version         Size        File name	 Platform
   ----------------------------------------------------------------------
   29-Jul-2005  01:00  8.11.50523.0       758,784  Mssdi98.dll   IA-64
   29-Jul-2005  01:00  7.10.3052.4        348,160  Msvcr71.dll   X86
   29-Jul-2005  01:00  2000.80.2151.0   1,187,840  Pfclnt80.dll  IA-64
   29-Jul-2005  01:00  2000.80.2151.0   1,061,376  Sqlagent.exe  IA-64
   29-Jul-2005  01:00  2000.80.2151.0     334,336  Sqldiag.exe   IA-64
   29-Jul-2005  01:00  2000.80.2151.0     246,784  Sqlfth75.dll  IA-64
   29-Jul-2005  01:00  2000.80.2151.0  24,954,368  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

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

Back to the top

To reproduce this problem, run the following code in SQL Query Analyzer:

BEGIN TRAN
BEGIN TRAN
SAVE TRAN test
UPDATE Northwind.dbo.Orders SET EmployeeID = 6 WHERE OrderID = 10248
COMMIT
EXEC [A linked server].master.dbo.sp_executesql @statement = N'UPDATE Northwind.dbo.Orders SET EmployeeID = 6 WHERE OrderID = 10248'
COMMIT

For more information about the SAVE TRANSACTION statement, visit the following Microsoft Web site:

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 is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top