• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 670
  • Last Modified:

Unable to mount exchange store

This is the scenarios:
SBS 2003 server stolen from client. I have a backup using ntbackup. Installed a "restore" server with the same name, ip address and domain name as the original server. Have restored the .edb and .stm files to the default location even though they were not in the default on the stolen box. Updated the "restore" server to what i think the stolen server was at with rehards to service packs and updates. When i try and mount the bd i get the following error:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

3 Solutions
Cliff GaliherCommented:
Exchange databases have AD data in them and rely on data in AD to mount. Therefore you must restore a system state or have another DC from the old domain to mount the databases. A new install, even with the same names and addresses, will have a new internal AD structure and the databases cannot be mounted. There is no way to force this.

If you cannot restore the server from backup then you will have to turn to 3rd party tools to extract mailboxes from the databases into pst files and import them I to the new installation.

Befor you restore need to  check the state of database whether its dirty or clean shut down using Eseutil /mh "Path of databse"
sentinelsystemsAuthor Commented:
State is dirty shutdown. Will it matter to continue if i cannot restore the system state?
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

Viral RathodConsultantCommented:
Please do nit restore the database,first perform the soft recovery if that is unsuccessfull then go a head and restore the database

This article will help you to bring the database is clean shutdown state.
sentinelsystemsAuthor Commented:
Before i continue with this process which can take very long, if i get it to a clean shutdown state, will i be able to continue if i cannot restore the system state as stated by cgaliher?
sentinelsystemsAuthor Commented:
Hi jimmithakkar, thanks for the link but I ask again, if I can't restore the system state will i be able to get the db mounted if i get it to a clean shutdown state?
Although I have never had need to personally do it, I believe you can mount an exchange database in a new forest (i.e. without restoring AD) it is caled an "Alternate forest recovery" it can be hard work but will work provided  certian pre-requisites need to be met



The Organization Name, Administrative Group Name, Storage Group Name, Mailbox Store (Server Name), and the LegacyExchangeDN Attribute on the recovery server must match that of the production machine.
Please refer to Microsoft Article IDs: KB813337, KB811063, KB322856, KB312371, KB312407, KB280652, KB271882, and KB324606 for further details


however if your databases are in a dirty shutdown state you will have to clean them up with eseutil to get them to mount. Try soft recovery first, and then /p (hard recovery) as a last resort. Once they are in a clean shutdon state ditch all the log files (keeping only the .stm and .edb files) and you should be able to mount them.

It is far easier though if you can restore AD as then all the mailboxes will be linked to users (the second article gives some details on recreating the accounts from info in exchange).

(trembling in trepidation at cliff's response)
sentinelsystemsAuthor Commented:
Ok, i have not had time to try and get the db up again and have resorted to purchasing software. I am however going to attemp this again and will post results.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now