FIX: Kill Then Net Session Loss Can Make Access Vio., Err 611
  
PSS ID Number: Q110985
Article last modified on 10-31-1994
 
4.20
 
Windows
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2
----------------------------------------------------------------------
 
BUG# NT: 642 (4.2)
 
SYMPTOMS
========
 
If you kill processes doing heavy tempdb inserts, then terminate the client
network sessions with net session/delete, under rare conditions, this may
generate an access violation followed by a server hang. Often error 611 is
seen. It will also sometimes happen if instead of net session/delete, you
just kill all the client sessions individually by rebooting all of the
client machines.
 
WORKAROUND
==========
 
Do not terminate net connections following use of Transact SQL kill
command.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 4.2. This problem was corrected in SQL Server version 4.21. For
more information, contact your primary support provider.
 
Additional reference words: 4.20 Windows NT
KBCategory: kbother kberrmsg
KBSubcategory: SSrvWinNT
 
=============================================================================
 
Copyright Microsoft Corporation 1994.
