Microsoft KB Archive/241646

{|
 * width="100%"|

XADM: Cannot Restore Unless at Least One Database Is Mounted

 * }

Q241646

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-

SYMPTOMS
If the Microsoft Exchange 2000 Server information store does not initialize the Extensible Storage Engine (ESE) for any storage group, it cannot initialize the ESE instance reserved for backup and restore, thus preventing all restore attempts.

WORKAROUND
To work around this situation, you must identify why the storage group does not start.

If the problem is that the database that the information store is trying to attach to is inconsistent, try to rename the checkpoint file, Edb.chk, to Edbchk.bak. This forces a full recovery, or "replay," of the log files. This approach may work to make the database consistent, allowing the information store to attach to this database.

If this method does not work, you must remove the inconsistent database files from the directory in which these files reside.


 * If you have a valid and tested backup, you may safely delete these files.
 * If no backup is present, it is highly recommended that you move these files to a different directory, located outside the Exchsrvr directory tree.

After the inconsistent databases have been removed from the file system, use the Microsoft Management Console (MMC) Exchange System Manager snap-in to mark the databases as Don't mount during start-up.

To apply the Don't mount during start-up property to a database, please refer to the following article in the Microsoft Knowledge Base:

"Q241644 XADM: Applying the Don't Mount During Startup Property to a Database" After the information store service starts successfully, you can restore the deleted or removed databases from backup.

MORE INFORMATION
This limitation is for Exchange 2000 Beta 3 only, and is slated to be fixed by RTM.

Additional query words:

Keywords :

Issue type : kbprb

Technology :