FIX: Access Violation May Occur If You Log Off After You Cancel A Linked Server Query (319962)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q319962
BUG #: 356450 (SHILOH_BUGS)

SYMPTOMS

After you follow these steps, you may receive an Access Violation (AV):
  1. You cancel a query against a linked server.
  2. You then disconnect the connection for the query.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later:
   Version      File name
   -------------------------

   8.00.599     Sqlservr.exe
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

MORE INFORMATION

When the access violation occurs, the following stack dump is written to the SQL Server error log:
Short Stack Dump
00866352 Module(sqlservr+00466352) (clean_tables_xact+00000095)
00531D6C Module(sqlservr+00131D6C) (clean_process+000000EA)
0053282C Module(sqlservr+0013282C) (kill_proc+000000EE)
00532DCA Module(sqlservr+00132DCA) (logout+000001AC)
00532C8F Module(sqlservr+00132C8F) (release_srvproc+00000045)
00411114 Module(sqlservr+00011114) (process_commands+00000280)
41073379 Module(UMS+00003379) (ProcessWorkRequests+0000024A)
41073071 Module(UMS+00003071) (ThreadStartRoutine+000000BD)
After the preceding stack dump occurs, either:

  • SQL Server quits unexpectedly.

    -or-

  • An assertion and the following stack dump occurs:
    Short Stack Dump
    0086EACF Module(sqlservr+0046EACF) (stackTraceException+0000004B)
    0086E8C4 Module(sqlservr+0046E8C4) (stackTrace+000002DB)
    00923F7F Module(sqlservr+00523F7F) (utassert_fail+000002E3)
    0086B85A Module(sqlservr+0046B85A) (ExecutionContext::Cleanup+00000118)
    005323CE Module(sqlservr+001323CE) (PSS::~PSS+0000012D)
    005322A1 Module(sqlservr+001322A1) (destroyPssMemory+00000019)
    005320AC Module(sqlservr+001320AC) (freepss+0000019D)
    005328B5 Module(sqlservr+001328B5) (kill_proc+00000209)
    00532DCA Module(sqlservr+00132DCA) (logout+000001AC)
    00532C8F Module(sqlservr+00132C8F) (release_srvproc+00000045)
    00411114 Module(sqlservr+00011114) (process_commands+00000280)
    41073379 Module(UMS+00003379) (ProcessWorkRequests+0000024A)<BR/>
    SQL Server Assertion: File: <proc.c>, line=1575 Failed Assertion = 'm_activeSdesList.Head () == NULL'.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbSQLServ2000sp3fix kbbug kbfix kbSQLServ2000preSP3fix KB319962