none
Database offline - Unable to remount Exchange 2013 RRS feed

  • Question

  • Hi all,

    I'm kinda pulling my hair out here. I had a power outage which looks to have corrupted the mailstore. Running eseutil /r and eseutil /d have completed successfully but the database still isn't mounting.

    I end up with this message:

    Couldn't mount the database that you specified. Specified database: Mailbox Database 2093613246; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionDatabaseError: Unable to mount database. (hr=0x80004005, ec=1108) Diagnostic context:    Lid: 65256      Lid: 10722   StoreEc: 0x454         Lid: 1494    ---- Remote Context Beg ----    Lid: 45120   dwParam: 0x569817    Lid: 57728   dwParam: 0x56995F    Lid: 46144   dwParam: 0x569A97    Lid: 34880   dwParam: 0x569A97    Lid: 34760   StoreEc: 0xFFFFFE0B    Lid: 46144   dwParam: 0x56A13F    Lid: 34880   dwParam: 0x56A13F    Lid: 54472   StoreEc: 0x1388        Lid: 42184   StoreEc: 0x454         Lid: 1750    ---- Remote Context End ----    Lid: 1047    StoreEc: 0x454      [Database: Mailbox Database 2093613246, Server: R-FS1.webrooster.local].

    I've tried restarting the server without any luck either.


    Any suggestions? (no backup to restore from unfortunately - that was my next shot)

    Friday, May 31, 2013 7:04 PM

Answers

All replies

  • Hi all,

    I have an issue where my mailstore has been corrupted following a power outage. I've run eseutil /r and eseutil /d on the database which has completed successfully, and inspecting the properties now shows the database in a clean shutdown state. However, I still can't mount the database, and get the following error.

    Couldn't mount the database that you specified. Specified database: Mailbox Database 2093613246; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionDatabaseError: Unable to mount database. (hr=0x80004005, ec=1108) Diagnostic context:    Lid: 65256      Lid: 10722   StoreEc: 0x454         Lid: 1494    ---- Remote Context Beg ----    Lid: 45120   dwParam: 0x569817    Lid: 57728   dwParam: 0x56995F    Lid: 46144   dwParam: 0x569A97    Lid: 34880   dwParam: 0x569A97    Lid: 34760   StoreEc: 0xFFFFFE0B    Lid: 46144   dwParam: 0x56A13F    Lid: 34880   dwParam: 0x56A13F    Lid: 54472   StoreEc: 0x1388        Lid: 42184   StoreEc: 0x454         Lid: 1750    ---- Remote Context End ----    Lid: 1047    StoreEc: 0x454      [Database: Mailbox Database 2093613246, Server: R-FS1.webrooster.local].

    Does anyone have any suggestions? (unfortunately no backup exists to restore from).


    Thanks,
    John

    Friday, May 31, 2013 7:13 PM
  • Hi all,

    I have an issue where my mailstore has been corrupted following a power outage. I've run eseutil /r and eseutil /d on the database which has completed successfully, and inspecting the properties now shows the database in a clean shutdown state. However, I still can't mount the database, and get the following error.

    Couldn't mount the database that you specified. Specified database: Mailbox Database 2093613246; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionDatabaseError: Unable to mount database. (hr=0x80004005, ec=1108) Diagnostic context:    Lid: 65256      Lid: 10722   StoreEc: 0x454         Lid: 1494    ---- Remote Context Beg ----    Lid: 45120   dwParam: 0x569817    Lid: 57728   dwParam: 0x56995F    Lid: 46144   dwParam: 0x569A97    Lid: 34880   dwParam: 0x569A97    Lid: 34760   StoreEc: 0xFFFFFE0B    Lid: 46144   dwParam: 0x56A13F    Lid: 34880   dwParam: 0x56A13F    Lid: 54472   StoreEc: 0x1388        Lid: 42184   StoreEc: 0x454         Lid: 1750    ---- Remote Context End ----    Lid: 1047    StoreEc: 0x454      [Database: Mailbox Database 2093613246, Server: R-FS1.webrooster.local].

    Does anyone have any suggestions? (unfortunately no backup exists to restore from).


    Thanks,
    John

    Friday, May 31, 2013 7:14 PM
  • Hi,

    Try moving the checkpoint and logs to a temporary location and mount database to see whether it works.

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com


    Simon Wu
    TechNet Community Support

    Tuesday, June 4, 2013 8:18 AM
  • have you tried to also use   /p   and   then  /mh to see the result, did it say "Dirty Shutdown"?

    Tuesday, June 4, 2013 8:39 AM
  • Hi,

    Is there any update on this thread?

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com


    Simon Wu
    TechNet Community Support

    Friday, June 7, 2013 2:07 AM
  • I'm with the same problem at this moment. My database say it's clean shutdown after a eseutil /p operation but it simply doesn't mount.
    Sunday, June 16, 2013 3:05 PM
  • Same problem here > repair succeeded, but can't mount it.

    [edit] ok, quite stupid... Didn't move the logfiles :-) .. after moving the logs to another location I was able to start it [/edit]

    • Edited by D_Goossens Friday, July 12, 2013 8:04 AM solved
    Friday, July 12, 2013 7:48 AM
  • I was in the same situation but the above steps sorted it out for me, but the steps could have been written better:

    Steps to fix:

    eseutil /mh *.edb

    eseutil /p *.edb

    eseutil /mh *.edb

    then I moved all the log files away from Exchange log folder :

    e:\Log\domain\

    to a log corupted storage

    * mean that you need to specifi the edb(mailbox DB) file is located.

    in my scenario it was these i ran:

    eseutil /mh e:\MailBox\domain\mail.edb

    eseutil /p e:\MailBox\domain\mail.edb

    Best Regards

    Rasmus Johnsen

    


    • Edited by Rasmus Johnsen Thursday, November 21, 2013 3:44 PM
    • Proposed as answer by Tonito Dux Tuesday, September 15, 2015 12:15 PM
    Thursday, November 21, 2013 3:44 PM
  • Hi,

    Try moving the checkpoint and logs to a temporary location and mount database to see whether it works.

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com


    Simon Wu
    TechNet Community Support


    it did not help
    Friday, February 14, 2014 10:56 AM
  • Hi All,

    Also remember to check that the drive that contains the database and logfiles, have enough free space available.

    I had an Exchange 2013 server with only 2GB space left on the drive with the exact same error. After I extended the drive, everything worked as intended and the database could be mounted.

    Regards,

    Morten.

    Wednesday, February 19, 2014 8:52 AM
  • Thank you sooooo much!!!  It worked like a charm !!
    Friday, July 25, 2014 8:06 PM
  • . CU6 update failed then I was left with a dirty shutdown and could not mount errors. 

    eseutil /mh *.edb /  eseutil /p *.edb / eseutil /mh *.edb fixed the dirty shutdown but I could not mount.  Moving the logs and chk file to a different location worked for me.

    Thanks

    Friday, September 12, 2014 3:56 PM
  • Hi even for me it fixed. I followed the steps above and moved the logs. DB Mounted!

    Thanks!

    Maurizio

    Tuesday, June 16, 2015 3:12 PM
  • After following the above steps, I'm able to mount the DB.

    Thanks alot.

    Tuesday, July 21, 2015 11:46 AM
  • Just a small clarification:

    If you don't move all the log files + 1 check file (E00.chk) from the DB folder you are trying to fix it won't work.

    • Proposed as answer by k31t4 Tuesday, June 27, 2017 2:00 PM
    Tuesday, September 15, 2015 12:18 PM
  • Thank you alll for the help in resolving this issue for me today.  It did work with the steps above but I had to stop the MS Exchange Information Store and MS Exchange DAG Management Services.  If I did not stop these two services, the E0*.chk and E0*.log files kept on creating new log entries.  

    Thanks again for saving my week.

    Thursday, November 3, 2016 5:07 PM
  • This worked perfectly.  After repair and moving the logs files, the databases mounted on their own.  Thanks so much!
    • Proposed as answer by k31t4 Tuesday, June 27, 2017 2:00 PM
    Sunday, April 16, 2017 5:28 AM
  • Thank you this just saved me.
    • Proposed as answer by RoodyH Monday, May 21, 2018 11:46 PM
    • Unproposed as answer by RoodyH Monday, May 21, 2018 11:46 PM
    Monday, November 6, 2017 3:04 AM
  • I was in the same situation but the above steps sorted it out for me, but the steps could have been written better:

    Steps to fix:

    eseutil /mh *.edb

    eseutil /p *.edb

    eseutil /mh *.edb

    then I moved all the log files away from Exchange log folder :

    e:\Log\domain\

    to a log corupted storage

    * mean that you need to specifi the edb(mailbox DB) file is located.

    in my scenario it was these i ran:

    eseutil /mh e:\MailBox\domain\mail.edb

    eseutil /p e:\MailBox\domain\mail.edb

    Best Regards

    Rasmus Johnsen

    


    Ramus' Steps worked perfectly.  Thank you so much
    • Proposed as answer by RoodyH Monday, May 21, 2018 11:48 PM
    Monday, May 21, 2018 11:48 PM
  • I was in the same situation but the above steps sorted it out for me, but the steps could have been written better:

    Steps to fix:

    eseutil /mh *.edb

    eseutil /p *.edb

    eseutil /mh *.edb

    then I moved all the log files away from Exchange log folder :

    e:\Log\domain\

    to a log corupted storage

    * mean that you need to specifi the edb(mailbox DB) file is located.

    in my scenario it was these i ran:

    eseutil /mh e:\MailBox\domain\mail.edb

    eseutil /p e:\MailBox\domain\mail.edb

    Best Regards

    Rasmus Johnsen

    


    Ramus' Steps worked perfectly.  Thank you so much

    I also wanted to show my appreciation for this.  Cheers.


    Thursday, May 31, 2018 3:33 PM
  • The drive on which the DataBase is placed, must have enough space. in my case the drive had 10 GB out of 135 GB and the Database was unable to mount. after creating some more space (total 30 GB free) the DB was able to mount. 
    Tuesday, January 29, 2019 5:44 AM
  • Thanks for save my life :D 
    Thursday, March 7, 2019 9:13 AM