BUG: Adding Several Defaults to Model Can Cause 602 Errors |
Q114846
The information in this article applies to:
- Microsoft SQL Server version 4.2x
BUG# 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 that is no longer used for SQL Server for Windows NT, sp_lookup. It has been reported that the 602 error 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.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.2. This problem does not occur in version 6.0.
Additional query words: Windows NT
Keywords : kbother kbprogramming
Issue type : kbbug
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ420OS2
Last Reviewed: October 26, 2000 |
