BUG: Adding Several Defaults to Model Can Cause 602 Errors

Last reviewed: April 29, 1997
Article ID: Q114846

The information in this article applies to:

  - Microsoft SQL Server version 4.2a for OS/2
  - Microsoft SQL Server version 4.2

BUG# OS/2: 1852 (4.2)

       NT:  777 (4.2)

SYMPTOMS

Creating several defaults in the model database can cause SQL Server to generate a 602 error when executing some stored procedures.

If more than seven defaults are created in the model database and SQL Server is then stopped and restarted, executions of existing stored procedures can start generating error 602:

   Msg 602, Level 21, State 3
   Could not find row in sysindexes for dbid '2', object
   '96003373', index '-1'.
   Run DBCC CHECKTABLE on Sysindexes.
   The SQL Server is terminating this process.

This does not happen on all stored procedures. In the bug replication, the only stored procedure that was always affected is a system stored procedure which is no longer used for SQL Server for Windows NT, sp_lookup. It has been reported that the 602 was observed on other stored procedures, but this could not be replicated.

WORKAROUND

Drop and recreate any affected stored procedures. If the problem occurs on system stored procedures, they can be restored using the scripts INSTMSTR.SQL, INSTCAT.SQL, ADMIN2.SQL, or OBJECT2.SQL in c:\Sql\Install.

NOTE: OBJECT2.SQL is not relevant to SQL Server 4.2a for OS/2.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.2 and SQL Server version 4.2a for OS/2. This problem does not occur in version 6.0.

Additional query words: Windows NT
Keywords : kbbug4.20 kbother kbprg SSrvServer SSrvWinNT kbother kbprg
Version : 4.2a | 4.2
Platform : OS/2 WINDOWS

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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.