FIX: You receive an “Error: 8526, Severity: 16, State: 2” error message in SQL Profiler when you use SQL Query Analyzer to start or to enlist into a distributed transaction after you have installed SQL Server 2000 SP4

Article translations Article translations
Article ID: 903742 - View products that this article applies to.
Bug #: 474469 (SQL Server 8.0)
Microsoft distributes SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
Expand all | Collapse all

On This Page

SUMMARY

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.

SYMPTOMS

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:

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
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:

Error: 8526, Severity: 16, State: 2
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.

CAUSE

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:
295027 Limited support for Savepoint in distributed transactions in SQL Server 2000 Service Pack 1

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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

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

After you apply the HOTFIX, you need to enable trace flag 8599 to workaround the issue. To do this apply one of the following two methods:
  • Method 1:

    Run the following code from the SQL Server Query Analyzer:
    DBCC TRACEON (8599,-1)
    NOTE You need to repeat this step every time SQL Server is stopped and restarted.

  • Method 2:

    If you want to have the 8599 trace flag turned ON permanently then:
    1. Stop the MSSQLServer service.
    2. Add -T8599 to the startup parameters. To do this, from Enterprise Manager:
      1. Right-click the servername, and then click Properties.
      2. In the Properties dialog box, click the General tab, and then click Startup Parameters .
      3. Add the traceflag (-T8599).
    3. Start the MSSQLServer service.

STATUS

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

MORE INFORMATION

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:
http://msdn2.microsoft.com/en-us/library/aa259178(SQL.80).aspx


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:
822499 New naming schema for Microsoft SQL Server software update packages
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:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 903742 - Last Review: October 9, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Workgroup Edition
Keywords: 
kbautohotfix kbqfe kbHotfixServer kbfix kbbug KB903742

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com