BUG: Orphaned Connection Processes Are Not Cleared

Last reviewed: April 8, 1997
Article ID: Q152059
The information in this article applies to:
  • Microsoft SQL Server, versions 4.21, 6.0 and 6.5

SYMPTOMS

When a SQL Server RPC session does not return for whatever reasons (for example, it is blocked on the remote server, or the remote server hangs), and the SQL client process that initiated the RPC session is terminated either normally or abnormally, SQL Server does not clean up the "ghost" or "orphaned" client connection process, even if the client session is already dropped at the network or operating system level.

If this ghost client process holds locks on some SQL Server objects, it will block other processes from accessing these objects as well. Trying to kill this client process will not work either. The only way to release the blocking is to reboot the SQL Server.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 4.21, 6.0, and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: ghost hang block lockup
Keywords : kbbug4.21 kbbug6.00 kbbug6.50
Version : 4.21 6.0 6.5
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.