Select the product you need help with

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 - View products that this article applies to.

Hotfix Download Available

Bug #: 364076 (SQL Server 8.0)

Expand all | Collapse all

Back to the top | Give Feedback

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 | Give Feedback

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:

<Date> <Time> spid52 clean_tables_xact: active sdes for tabid 409768517
<Date> <Time> spid52 Process 52 unlocking unowned resource: TAB: 13:409768517 []
<Date> <Time> spid52 Error: 1203, Severity: 20, State: 1
<Date> <Time>spid52 Process ID 52 attempting to unlock unowned resource TAB: 13:409768517 []

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

290211

(http://support.microsoft.com/kb/290211/ )

How to obtain the latest SQL Server 2000 service pack

Back to the top | Give Feedback

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

(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

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

(http://support.microsoft.com/kb/290211/ )

How to obtain the most recent SQL Server 2000 service pack

Restart information

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

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 | Give Feedback

STATUS

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

Back to the top | Give Feedback

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

(http://support.microsoft.com/kb/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

(http://support.microsoft.com/kb/824684/ )

Description of the standard terminology that is used to describe Microsoft software updates

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 | Give Feedback