FIX: Handled Access Violation on INSERT Through Cursor (263649)
The information in this article applies to:
This article was previously published under Q263649
BUG #: 57044 (SQLBUG_70)
SYMPTOMS
Microsoft SQL Server 7.0 might generate a handled Access Violation (AV), when all of the following conditions are met:
- You use a server based cursor.
- You use a keyset cursor.
- You insert data into a table.
- The first INSERT inserts data into all the columns, except one. The second INSERT inserts data into all of the columns.
The following error message might occur on the client:
ODBC: Msg 0, Level 19, State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler: Process 7 generated fatal exception 0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
WORKAROUND
To work around this problem, try either of the following: - Use a client based cursor.
-or-
- Use a dynamic cursor.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Modification Type: | Major | Last Reviewed: | 3/14/2006 |
---|
Keywords: | kbBug kbfix kbQFE KB263649 |
---|
|