XADM: Database in Inconsistent State After Soft Recovery

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q166542

Expand all | Collapse all

SYMPTOMS

If your system crashes after the Jet database has completed recovery from a previous crash, but before any subsequent log records are flushed, the database is in an inconsistent state. A -550 error recorded from source EDB may appear in the application log.

Back to the top

CAUSE

The RecoveryQuit transaction from the first recovery operation is in the last log file when another recovery is attempted.

Back to the top

RESOLUTION

Apply the fix described below. Jet's soft recovery was fixed to handle the existence of a RecoveryQuit transaction in the last log file. This allows the second recovery to complete.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange Server 5.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Back to the top

APPLIES TO

Microsoft Exchange Server 5.0 Standard Edition

Back to the top

kbbug KB166542

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top