FIX: Unhandled Access Violation with Temporary ProcedureLast reviewed: April 8, 1997Article ID: Q153079 |
The information in this article applies to:
SYMPTOMSWhen 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.
WORKAROUNDUse 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 INFORMATIONThe SQL Server errorlog (under SQL..\LOG directory on the server) would look like: Error : 631, Severity: 21, State: 1 spid12 The length of 116 passed to delete row routine for the row atoffset 32 is incorrect on the following page: Page pointer = 0xa8b000, pageno = 104, status = 0x101, objectid = 6, indexid = 0 kernel WARNING: Process being freed while holding Dataserver semaphoreError : 631, Severity: 21, State: 1 The length of 116 passed to delete row routine for the row at offset 32 is incorrect on the following page: Page pointer = 0xa8b000, pageno = 104, status = 0x101, objectid = 6, indexid = 0 kernel udread: Operating system error 6(The handle is invalid.) on device 'C:\SQL60\DATA\MASTER.DAT' (virtpage 0x000002fb).Buffer 8d8700 from database 'master' has page number 0 in the page header and page number 759 in the buffer header Recursive error 822 in ex_print kernel mirrorproc: i/o error on primary device 'C:\SQL60\DATA\MASTER.DAT' STATUSMicrosoft 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |