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

Exchange 2010 - Unable to mount Database

Hi, I have quite a problem on my hands and have been working on it for a few hours with no success. Firstly i dont have a recent enough backup, so i cannot restore. (i know, but there is nothing i can do about it now)

The machine went a bit screwy over the weekend and was stuck on a reboot screen when they came in this morning. Everything but exchange came right on a hard reboot.

The EMC tells me that "Mailbox Database" is dismounted. When trying to mount i get gives the error output below.


--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database 'Mailbox Database'.

Mailbox Database
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)
. [Database: Mailbox Database, Server: SERVER.rapidspillrespo.local].

An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)
. [Database: Mailbox Database, Server: SERVER.rapidspillrespo.local]

An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)
. [Server: SERVER.rapidspillrespo.local]

MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)


After a whole lot of ggling i have:
Restarted the server again.
Restarted all Exchange services quite a few times in between tries.
run an ESEUTIL /r
ESEUTIL /p
eseutil /ml
checked that it is CLEAN Shutdown
deleted 216Gb of logs

but i still get the same -515 error.

Please help?
0
RichJS
Asked:
RichJS
3 Solutions
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Did you move the .log .jrs and .chk as well ?
Is there any event ID in the App logs ? Please check and share the event ID

Was the Exchange re-installed ? If so what is the current SP ?

DB might be very much corrupted if even after Repair its not comming up ? Anyways we will try few things :)

Always be open for 3rd party to extract data from corrupted .edb files

Ontrack - Kernel (few 3rd party softwares)

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Wait ... if the users use Outlook cache mode you can export the data from OST to PST while the Mailbox Database is dismounted :)

If users in cache mode ... please do not mount blank DB rather quickly take data to PST to have no data loss ..... so once all is in PST we can mount Blank DB and Import if required :)

- Rancy
0
 
RichJSAuthor Commented:
no, just the .log files.

Exchange 2010 on SBS 2011

I've been looking for something that might make it easy to create a new store and distribute the PSTs or something to each user. Thare arent too many for it to be a big hassle.


Event ID:      454
Description:
Information Store (3276) Mailbox Database: Database recovery/restore failed with unexpected error -515.


Event ID:      9519
While starting database Mailbox Database, the following error occurred: 0xfffffdfd.  
Failed to configure MDB.

Event ID: 9519
While starting database Mailbox Database, the following error occurred: 0xfffffdfd.  
Start DB failed..


EventID:231
At '2012/08/27 06:32:21 PM', the copy of database 'Mailbox Database' on this server encountered an error during the mount operation. For more information, consult the Event log on the server for "ExchangeStoreDb" or "MSExchangeRepl" events. The mount operation will be tried again automatically.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
RichJSAuthor Commented:
i looked into that, but it is a very intensive operation. I would prefer to get the thing mounted instead. are there tools to allow creation of separate PSTs for each mailbox from the EDB? because that will have me up and running quite quickly then...
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
As i said there are but if the state of EDB is too bad compared to our assumption ... we might end loosing data ..... sp best is to get PST from OST .... no extra cost just a bit of work i agree :(

- Rancy
0
 
RichJSAuthor Commented:
i'm just busy installing Exchange 2010 SP2 and then i'll try it again.
I'm willing to buy SP to extract the PSTs from the EDB, ive already downloaded the trial, so i will see how it manages if its badly corrupt, but i'm still waiting for everything to complete first. I'm really hammering this poor CPU with all the work i'm giving it today. :)
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Would be a good day if all ends good and after all the work the CPU will also get some rest :)

- Rancy
0
 
RichJSAuthor Commented:
Just sorted it out after a marathon session.

This is what i did:

Link-> Virtual Helpme - Exchange 2010 Error: Unable to mount database
ran :
eseutil /mh "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"
found State: Dirty Shutdown
ran :
eseutil /p "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"
and then re-ran eseutil /mh  and found Clean Shutdown.
As a sidenote, if the database state is Clean Shutdown you can safely remove the logs.
Then i cut all log files from
C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database
and pasted them elsewhere (for deletion later if all goes right.)

i attempted to re-mount and it still didn't work.

i rebooted and found the error had now changed to ec=-528 when attempting to mount.

link-> Experts Exchange - Cannot Mount Database in Exchange Server 2010 missing log file
I did a bit more digging on the interwebs and found that tmp.edb and e00tmp.log can be moved and recreated. So i cut and moved them, created blank .txt files and renamed them  
tmp.edb
and
e00tmp.log
Tried to mount one more time and it hopped right on and outlook connected instantly.

Check your mailboxes to make sure everything is there, and go ahead and delete the log files if everything is as it should be.

There was probably a much more straight forward way, but this fixed it. Hope it helps someone else too. :)
1
 
RichJSAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for RichJS's comment #a38338830

for the following reason:

After a lot of digging on the web and reading through pages and pages of info i put together different steps that eventually worked. since it was an urgent matter, i could not wait for more input and managed to find the solution myself.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I guess i asked you all possible thing to move all files apart the .edb and also if the server was re-installed to get it to the same SP and then it did the trick .... nothing different.

I guess i should be awarded points ..... but wont Object will leave to you to take the decision :)

- Rancy
0
 
Kernel_Recovery_ToolsCommented:
Check and Repair the database,
Check whether the database state is dirty or clean.
If database state is dirty you have to repair database first and it state is clean then you can go directly for mount the database.
May be database state is clean but some of log is creating issue, for that we have to check using chkdsk utility.


How to check the database:

Run eseutil /mh "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"

Look for the following in the output: State: Dirty Shutdown

2 Database is not properly shut down so it should be repiared first.

Before attempting any kind of repiar make sure you have backup of database.


To repairthe database, run the following command:

eseutil /p "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"

3 Re-run the database check from Run eseutil /mh "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb" and if all goes well, you should see this somewhere in the output: State: Clean Shutdown

 

You can try mounting the database. If it mounts, you are good to go, if it doesn't you have to check the logs:
Check and Repair the database logs

4 Check the exchange logs (don't forget to specify E00 - the starting sequence for the logs)

eseutil /ml "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E00"

5 There will be a list of logs and depending on their state, you may get an error. (They should all say OK, if the logs are clean) Errors vary, but most likely it is a file corruption and needs a chkdsk to run.
if the database state is Clean Shutdown you can safely remove the logs.
0
 
RichJSAuthor Commented:
This was a good fallback should the database not be repairable.  Thanks Rancy!
0
 
RichJSAuthor Commented:
After a lot of digging on the web and reading through pages and pages of info i put together different steps that eventually worked. since it was an urgent matter, i could not wait for more input and managed to find the solution myself.
0
 
Marshal HubsEmail ConsultantCommented:
Use following article to resolve fail to mount error: https://www.stellarinfo.com/article/solved-exchange-database-fails-to-mount.php
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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