FIX: Unexpected Close of a SQL Server Connection May Lead to an Access Violation (323118)



The information in this article applies to:

  • Microsoft SQL Server 7.0

This article was previously published under Q323118
BUG #: 102682 (SQLBUG_70)

SYMPTOMS

An unexpected close of a SQL Server connection (for example, when a connection is closed by using the Transact-SQL KILL command) may lead to a write of data that is not valid into a SQL Server buffer pool page. This problem may later result in an access violation with a SQL Server thread.

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.

To resolve this problem, 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 usual 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 has the file attributes (or later) 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.
   Version      File name
   -------------------------

   7.00.1072    Opends60.dll
				
Note: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


WORKAROUND

To work around this problem, reduce or stop the use of commands such as Transact-SQL KILL to avoid an unexpected close of a SQL Server connection.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/18/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE kbSQLServ700preSP5fix KB323118