FIX: Terminating Clients with TSQL KILL May Cause ODS AV (238620)



The information in this article applies to:

  • Microsoft SQL Server 6.5

This article was previously published under Q238620
BUG #: 18736 (SQLBUG_65)

SYMPTOMS

Using the Transact-SQL KILL statement to terminate a SQL Server server process ID (SPID) that originated from a TCP/IP Net-Library client can result in a handled access violation (AV) within Open Data Services (ODS), which results in a shutdown of SQL Server.

When such an ODS AV occurs, you can see the following stack dump output in the error log:
server ***********************************************************
server *
server * STACK DUMP:
server *
server * Exception Address = 25A21960

RESOLUTION

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

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Version       File name     Platform
   ------------------------------------
   6.50.462      sql462i.exe   Intel
   6.50.462      sql462a.exe   Alpha
				
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.


WORKAROUND

To work around this problem, avoid frequently using the Transact-SQL KILL statement. Doing this reduces the probability of encountering this access violation.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 6.5.

Modification Type:MinorLast Reviewed:10/7/2005
Keywords:kbBug kbfix kbQFE KB238620