BUG: Orphaned Connection Processes Are Not Cleared (152059)
The information in this article applies to:
- Microsoft SQL Server 4.2x
- Microsoft SQL Server 6.0
- Microsoft SQL Server 6.5
This article was previously published under Q152059 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.
| Modification Type: | Minor | Last Reviewed: | 3/14/2005 |
|---|
| Keywords: | kbBug KB152059 |
|---|
|