BUG: Errors 603, 3313 and 3414 May Mark Database as Suspect

• Microsoft SQL Server, version 6.0 Service Pack 3

SYMPTOMS

When the computer running SQL Server is either going through a recovery or loading transaction logs, a database may be marked as suspect, with the following error messages:

Error 603 Level 19 There are not enough system session descriptors
available to run this query. The maximum number available to a process
is %d. Split query and rerun.

Error 3313 level 10 Error while redoing log row in database '%.*s'. %S_RID.

Error 3414, "Database '%.*s' (dbid %d): Recovery failed. Please contact Technical Support for further instructions.

WORKAROUND

To work around this problem, follow the steps below:

1. Use the stored procedure sp_resetstatus to change the database's status from suspect to normal.



2. Shut down the computer running SQL Server.



3. Replace the Sqlservr.exe file with a copy of Sqlservr.exe prior to SQL Server 6.0 Service Pack 3. Make sure to preserve the SQL Server Service Pack 3 copy of Sqlservr.exe.



4. When SQL Server is restarted, recovery should complete correctly. Shut down the computer running SQL Server once more.



5. Reverse the procedure of Step 3 above, replacing the current copy of Sqlservr.exe with the one from SQL Server Service Pack 3.



6. Restart the computer running SQL Server, which should now function properly.

STATUS

Microsoft has confirmed this to be a problem in SQL Server versions 6.0 Service Pack 3.

A supported fix is now available for version 6.0, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords          : kbusage SSrvGen kbbug6.00.sp3 
Version           : 6.0 SP3
Platform          : WINDOWS 
Issue type        : 

Last Reviewed: April 2, 1999