Microsoft KB Archive/814654

= FIX: Error 1203 may be logged in the error log when you disconnect from an instance of SQL Server 2000 after you submit queries or transactions =

Article ID: 814654

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 Desktop Engine (Windows)
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



Bug #: 364076 (SQL Server 8.0)



Article contents

 * Summary
 * Symptoms
 * Resolution
 * Hotfix information
 * Prerequisites
 * Restart information
 * Hotfix file information
 * Status
 * More Information
 * Stack information



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.
 * The files that are contained in the hotfix package.

back to the top



SYMPTOMS
When you disconnect from an instance of Microsoft SQL Server 2000 after you submit queries or transactions, error 1203 may be logged in the SQL Server error log. Subsequently, an access violation exception may occur. This access violation exception causes SQL Server 2000 to close, and an error message that is similar to the following is logged in the SQL Server 2000 error log:

spid52 clean_tables_xact: active sdes for tabid 409768517

spid52 Process 52 unlocking unowned resource: TAB: 13:409768517 []

spid52 Error: 1203, Severity: 20, State: 1

spid52 Process ID 52 attempting to unlock unowned resource TAB: 13:409768517 []

For a list of previous hotfixes, see the &quot;Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes&quot; section in the following Microsoft Knowledge Base article:

290211 How to obtain the latest SQL Server 2000 service pack

back to the top



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

back to the top

Prerequisites
You must install SQL Server 2000 Service Pack 3 (SP3). For more information about how to obtain SQL Server 2000 SP3, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the most recent SQL Server 2000 service pack

back to the top

Restart information
You do not have to restart your computer after you apply this hotfix.

back to the top

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 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 item in Control Panel. Date        Time   Version            Size    File name

30-Jan-2003 00:18  7.0.9466.0        344,064  Msvcr70.dll 30-Jan-2003 00:18  2000.80.722.0      57,904  Osql.exe 30-Jan-2003 00:18  2000.80.534.0     127,548  Sqdedev.dll 30-Jan-2003 00:18  2000.80.194.0     180,290  Sqlunirl.dll 30-Jan-2003 00:55                        180  Drop_repl_hotfix.sql 31-Jan-2003 23:32  2000.80.763.0   1,557,052  Dtsui.dll 30-Jan-2003 04:18                    746,470  Instdist.sql 30-Jan-2003 00:55                      1,402  Inst_repl_hotfix.sql 08-Feb-2003 05:40  2000.80.765.0      90,692  Msgprox.dll 08-Feb-2003 02:53                  1,065,895  Replmerg.sql 08-Feb-2003 05:40  2000.80.765.0     221,768  Replprov.dll 08-Feb-2003 05:40  2000.80.765.0     307,784  Replrec.dll 30-Jan-2003 04:18                  1,084,318  Replsys.sql 08-Feb-2003 05:40  2000.80.765.0     176,696  Sqlmap70.dll 08-Feb-2003 05:40  2000.80.765.0      57,920  Sqlrepss.dll 08-Feb-2003 05:41  2000.80.765.0   7,528,529  Sqlservr.exe 08-Feb-2003 05:40  2000.80.765.0      45,644  Sqlvdi.dll 08-Feb-2003 05:40  2000.80.765.0      82,492  Ssnetlib.dll Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

back to the top



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

back to the top



MORE INFORMATION
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 Microsoft uses to describe 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

back to the top

Stack information
The short stack that is associated with this access violation may be similar to the following short stack:

77EAB2F0 Module(KERNEL32+0002B2F0) (RaiseException+00000056)

0087C7CA Module(sqlservr+0047C7CA) (stackTraceException+0000004B)

0087C5BE Module(sqlservr+0047C5BE) (stackTrace+0000033C)

00931097 Module(sqlservr+00531097) (utassert_fail+000002E3)

008793DF Module(sqlservr+004793DF) (ExecutionContext::Cleanup+00000118)

00505A02 Module(sqlservr+00105A02) (PSS::~PSS+00000130)

005058D2 Module(sqlservr+001058D2) (destroyPssMemory+00000019)

005056D3 Module(sqlservr+001056D3) (freepss+0000019D)

005061A6 Module(sqlservr+001061A6) (kill_proc+00000209)

00506513 Module(sqlservr+00106513) (logout+000001AC)

005063D8 Module(sqlservr+001063D8) (release_srvproc+00000045)

004270F9 Module(sqlservr+000270F9) (process_commands+000002A2)

41075002 Module(UMS+00005002) (ProcessWorkRequests+00000272)

41074698 Module(UMS+00004698) (ThreadStartRoutine+00000098)

7800C9EB Module(MSVCRT+0000C9EB) (beginthread+000000CE)

back to the top

Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB814654

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.