BUG: 1105 During Object Resolution Can Cause Thread AV

 Last reviewed: April 30, 1997
Article ID: Q132225
The information in this article applies to:
  • Microsoft SQL Server, version 4.21a
BUG# NT: 9690 (4.21a)

SYMPTOMS

When an object, such as a stored procedure or view, is undergoing resolution and the process encounters or causes an 1105 error in syslogs, it can cause a thread access violation or 707 error: 

   Attempt to access memory at location 0x0
Two errors are returned to the client process. The client receives the 1105 error on syslogs message, and then receives the access violation or the 707 error. The SQL Server errorlog, however, will only record the access violation or the 707 error.

CAUSE

The resolution process incorrectly handles an 1105 error on syslogs situation. When this happens, additional rows are added to the sysprocedures table, consequently the reason for the 1105 error.

WORKAROUND

Clear the transaction log by dumping it and resume normal processing. Also, you may want to drop and recreate the object if the size of the object has grown significantly.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.21a. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

This problem does not occur in SQL Server version 6.0.

Additional query words: gp fault gpf Windows NT
Keywords : kbbug4.21a kbother SSrvWinNT
Version : 4.21a
Platform : WINDOWS
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.