FIX: Unhandled Access Violation with Temporary Procedure (153079)
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 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.
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.
Modification Type: | Major | Last Reviewed: | 11/14/2003 |
---|
Keywords: | kbBug kbfix kbnetwork KB153079 |
---|
|