XADM: Exchange 2000 SP2 Does Not Allow You to Restore Exchange 2000 or Exchange 2000 SP1

Article translations Article translations
Article ID: 316794 - View products that this article applies to.
This article was previously published under Q316794
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

After you upgrade to Exchange 2000 Server Service Pack 2 (SP2) from the Release to Manufacturing (RTM) version of Exchange 2000 Server or Exchange 2000 Server Service Pack 1 (SP1), you may not be able to restore your earlier Exchange 2000 or Exchange 2000 SP1 backups to the Exchange 2000 SP2 server.

The following error messages may be logged in the Application event log:
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 411
Date: 1/22/2002
Time: 5:50:27 PM
User: N/A
Computer: E2KGSZ
Description:
Information Store (2696) Restore0001: The log version stamp of logfile d:\temp\First Storage Group\E0000004.log does not match the database engine version stamp. The logfiles may be the wrong version for the database.

For more information, click http://search.support.microsoft.com/search/?adv=1.

Event Type: Error
Event Source: ESE BACKUP
Event Category: Callback
Event ID: 904
Date: 1/22/2002
Time: 5:50:27 PM
User: N/A
Computer: E2KGSZ
Description:
Information Store (2696) Callback function call ErrESECBRestoreComplete ended with error 0xC8000202 The version of the log file is not compatible with the version of the Microsoft Exchange Server database (EDB).

For more information, click http://search.support.microsoft.com/search/?adv=1.

Event Type: Error
Event Source: ESE BACKUP
Event Category: Recovery
Event ID: 903
Date: 1/22/2002
Time: 5:50:27 PM
User: N/A
Computer: E2KGSZ
Description:
Information Store (2696) Restore from directory d:\temp\First Storage Group ended with error (Error returned from an ESE function call (-514). ).

For more information, click http://search.support.microsoft.com/search/?adv=1.
Because you did not successfully complete the restoration, if you check with Eseutil /MH, the databases are inconsistent, which is expected.

If you attempt to mount the databases manually after the restoration, you may receive the following error message:
An internal processing error has occurred. Try starting the Exchange System Manager or the Microsoft Exchange Information Store, or both.

ID no: c1041724
Exchange System Manager
If you attempt to mount the databases manually after the restoration, the following error messages may also be logged in the Application event log:
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 619
Date: 1/22/2002
Time: 5:52:10 PM
User: N/A
Computer: E2KGSZ
Description:
Information Store (2696) Attempted to attach database
'C:\MDBDATA\priv1.edb' but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.

For more information, click http://search.support.microsoft.com/search/?adv=1.

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: 1/22/2002
Time: 5:52:10 PM
User: N/A
Computer: E2KGSZ
Description:
Error 0xfffffde0 starting database "First Storage Group\Mailbox Store (E2KGSZ)" on the Microsoft Exchange Information Store. Failed to attach to Jet DB.

For more information, click http://search.support.microsoft.com/search/?adv=1.

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 1/22/2002
Time: 5:52:10 PM
User: N/A
Computer: E2KGSZ
Description:
Error 0xfffffde0 starting Storage Group
/DC=COM/DC=TESTDOM/DC=GS/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=TESTORG/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=E2KGSZ/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store.
MDB failed to start.
NOTE: For brevity, only messages with an event type of "Error" are included; all messages with an event type of "Information" are excluded.

CAUSE

This issue can occur because in Exchange 2000 SP2, the databases are upgraded to a newer version. Because of this database upgrade in Exchange 2000 SP2, earlier backups that were created before you applied Exchange 2000 SP2 cannot be restored to an Exchange 2000 SP2 system.

WORKAROUND

To work around this issue if you need to remove an Exchange 2000 SP2 upgrade and put an earlier Exchange 2000 installation in its place, you must restore the original system state, file system, transaction logs, and database.

NOTE: If you restore an Exchange 2000 SP2 backup to an Exchange 2000 or Exchange 2000 SP1 installation, the event ID 619 and 9518 error messages that are described in the "Symptoms" section may be logged and the databases may not mount. However, in this case, you can simply upgrade to Exchange 2000 SP2, and then mount the databases.

MORE INFORMATION

Because backups that were created before you applied Exchange 2000 SP2 cannot be restored to an Exchange 2000 SP2 system, make sure that you back up your server immediately before and immediately after you apply Exchange 2000 SP2.

Create backups of your server to ensure that you have a valid backup of your servers if you need one. This is considered the best practice for all upgrades.

For additional information about the issues that are described in this article, see the following documents:
SP2 Deployment Guide, Section titled Removing Service Pack 2
SP2 Release Notes, Section titled Upgrading to SP2

Properties

Article ID: 316794 - Last Review: October 24, 2013 - Revision: 2.3
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kberrmsg kbprb KB316794

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