Hello, I have an Exchange Server 2010 server that was shut down improperly, so now the database is not automatically mounted when I try to manually mount it reports missing files and assemble suggests creating a new .edb file, but the original .edb file and the log files are in the folder, are all there.

Already performed these procedures found below, but not solved.

http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/

Note: We do not have the backup of the database, then we must ride it without having to use backup features.

Any suggestion?

1. Whats the state when you run  eseutil /mh?  i.e. consistent/inconsistent or dirty/clean
2. You ran a /P as well, if so did you make a backup copy of the EDB prior to running the /
3. I'll try to help you resolve the issue with the DB, however if it persist our DigiScope product may be able to open the offline copy of the EDB using the Forensic mode and once inside you can recover the contents to a dial toned version of the EDB

Hi,

Thank you for your question.

We could check if there are any errors in application log and send the log to ibsexc@microsoft.com for our troubleshooting(include the error when we mount the database).

First of all, we should make sure the Exchange server could connect to DC without any problems. Then also refer to the following link to check if the issue persist:

https://support.microsoft.com/en-us/kb/896143?wa=wsignin1.0

in addition, make sure the service which is Microsoft Exchange Information Store is running on Exchange mailbox server. If we could not mount the database, we could restart it to check if the issue persist.

There are some similar cases for us to refer:

https://social.technet.microsoft.com/Forums/office/en-US/d64668da-6c1b-4acd-8339-aa28d586feb0/database-wont-mount-due-to-missing-log-file?forum=exchangesvrgenerallegacy

http://blogs.technet.com/b/mspfe/archive/2012/09/06/why-exchange-databases-might-remain-dirty-after-eseutil-r-recovery.aspx

https://social.technet.microsoft.com/Forums/exchange/en-US/4d1f1ec0-afa7-4a97-af2c-896f3d3c2abb/failed-to-mount-database-mailbox-database-hr0x80004005-ec528  

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hello friends, Already performed the esetutil with various options with / r with / d with / l following the instructions found on some internet sites, performed exactly this way the command that is here eseutil / R E00 / l "c: \ FolderDB" / d "c: \ FolderDB" Others also performed. But the database does not mount, and always the same mnsagem "At least one of this store's file is Missing. Mount the force store will force the creation of an empty database .............. ...!" When you run the eseutil / mh, I see that the status of the database is with the status of Clean Shutdown. Does anyone here have any more ideas? What is missing for the database finally up? Thank you!

Hello friends, Already performed the esetutil with various options with / r with / d with / l following the instructions found on some internet sites, performed exactly this way the command that is here eseutil / R E00 / l "c: \ FolderDB" / d "c: \ FolderDB" Others also performed. But the database does not mount, and always the same mnsagem "At least one of this store's file is Missing. Mount the force store will force the creation of an empty database .............. ...!" When you run the eseutil / mh, I see that the status of the database is with the status of Clean Shutdown. Does anyone here have any more ideas? What is missing for the database finally up? Thank you!

Maybe during the power failure, the information that tells Exchange where the DBs are located got corrupted?  Try

get-mailboxdatabase | select edbfilepath

and make sure that it still thinks the files are in C:\FolderDB (or whatever you called it).

Maybe during the power failure, the information that tells Exchange where the DBs are located got corrupted?  Try

get-mailboxdatabase | select edbfilepath

and make sure that it still thinks the files are in C:\FolderDB (or whatever you called it).

I gave up work this out.

So I created a new database, removed the Exchange users and'm creating them again and placing them in the new database, the stations the technico staff are exporting the OST file to PST, then create a new user account Outlook and import the PST.

It's work, but I can not waste time, this Exchange Server is stopped there two days, we'll see if now at least create the necessary backup routines, as the company has the Symantec Backup Exec and was not being used to protect data Exchange.

Thank you all!

I gave up work this out.

So I created a new database, removed the Exchange users and'm creating them again and placing them in the new database, the stations the technico staff are exporting the OST file to PST, then create a new user account Outlook and import the PST.

It's work, but I can not waste time, this Exchange Server is stopped there two days, we'll see if now at least create the necessary backup routines, as the company has the Symantec Backup Exec and was not being used to protect data Exchange.

Thank you all!