FIX: Error Message 602 During Recovery of a Database

Article translations Article translations
Article ID: 279793 - View products that this article applies to.
This article was previously published under Q279793
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57641 (SQLBUG_70)
Expand all | Collapse all

Symptoms

If a table with an identity column is created and then subsequently dropped in the same transaction, and this transaction does not commit before the server shuts down abnormally, recovery of the database may fail with the following error message:
Error: 602, Severity: 21, State: 16.
Cannot recover the %databasename% database.
Be aware that you cannot associate all suspect databases with this issue. This problem is very timing-specific. The time between when the drop table command is executed and the server shuts down abnormally is important.

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.

More information

This problem is prevented with the application of SP3. However, SP3 does not resolve the issue if the customer has a database that is suspect. The customer still needs to restore from a backup or contact technical support for the usual assistance with a suspect database.

Properties

Article ID: 279793 - Last Review: November 2, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB279793

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com