Now, I’ve taken a couple Exchange courses. They cover all the bases… expect when things go wrong. That’s why it’s nice to have labs… today in my Lab I discovered I was unable to get email from my exchange server, neither from activeSync nor Outlook Web App (OWA).
Something went wrong alright… first thing I noticed was my disk had run out of space… whoops. Hahaha. Expand the drive, reboot and… Something Went Wrong…
Sigh…. alright event viewer… what ya got for me…
Unable to mount…. I guess it didn’t like what happened to the DB after the disk ran out of space… some quick googling (1 and 2 copy cats… and can’t even tell you the DB file locations…) and one more, more personal blog post.
Exchange Default DB File Locations
If you are using Exchange Server 2000 & 2003, you can locate your EDB files at:
If you are using Exchange Server 2007, you can locate your EDB files at:
C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb
C:\Program\Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Public Folder Database.edb
If you are using Exchange Server 2010, you can locate your EDB files at:
C:\Program Files\Microsoft\Exchange Server\V14\Mailbox Database\Mailbox Database.edb
C:\Program Files\Microsoft\Exchange Server\V14\Public Folder Database\Public Folder Database.edb
If you are using Exchange Server 2013, you can locate your EDB files at:
C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox database Name\Mailbox database Name.edb
If you are using Exchange Server 2016, you can locate your EDB files at:
C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database Name.edb
Repairing the Exchange Mailbox Database
Which they all tell you to use a cool old “tool” eseutil. which seemed straight forward, ensure you run an elevated cmd or you won’t have access to the directory path of the exchange DB file. In my case I used the Exchange 2013 path which was the version used in my lab.
I also moved the log files:
move *.log c:\temp
Yeah… that took a lil while.
Mounting the Exchange Mailbox Database
Once it’s repaired used Exchange Mgmt Shell to mount it:
Whoops, silly me, since everyone said to stop the information store service I did… so after starting the service, and rerunning the command it succeeded.
Which resulted in:
- Check the source of the Database Corruption. (Mine was Disk Space)
- Stop the Information Store Service
- Check the Validity of the Mailbox Database (eseutil /mh)
- Repair if required (eseutil /p)
- Restart the Exchange Information Store Service
- Mount the Mailbox Database
Hope this helps someone.