Article ID: 153079
Article Last Modified on 11/14/2003
APPLIES TO
- Microsoft SQL Server 4.21a Standard Edition
- Microsoft SQL Server 6.0 Standard Edition
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q153079
SYMPTOMS
When a temporary stored procedure is created and executed within a user- defined transaction and the client (DBLIB or ODBC) disconnects without either committing or rolling back the transaction, SQL Server stops running. The SQL Service manager shows a red light.
An attempt to kill the process that initiated the transaction also causes an Unhandled Access Violation error.
WORKAROUND
Use a permanent stored procedure instead of a temporary stored procedure within a transaction.
You can also commit or roll back the transaction before the client disconnects.
MORE INFORMATION
The SQL Server errorlog (under SQL..\LOG directory on the server) would look like:
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.
Additional query words: sp1
Keywords: kbbug kbfix kbnetwork KB153079