none
MapiExceptionJetErrorRequiredLogFile sMissing: Unable to mount database. (hr=0x80004005, ec=-543)

    Question

  • Dear Team,

    we have Exchange server 2007.

    Today unexpert power failure, so the server is down. after turn on the server database dismounted.

    Totaly 4 Storage group, each group has 4 databases.

    2 Storage group all databases are successfully mounted, no issue.

    but 2 storage group, all databases are dismounted.

    am trying to do mount, getting an error.

    -------------------------------------------------------------------------

     At least one committed transaction log file is missing. Mounting this database
    will result in data loss. Do not take this action unless you cannot locate the
    missing log files. Are you sure you want to continue?
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help
    (default is "Y"):y
    Mount-Database: Exchange is unable to mount the database that you specified. Specified database: "database name"; Error code: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database. (hr=0x80004005, ec=-543)

    -------------------------------------------------------------------------------

    Database status is:-

    State: Dirty Shutdown

    please help us to resolve the issue.

    no database backup available.

    please help me the best way - try to mount the database - without data loss or less data loss.



    Regards, Pradhap P


    • Edited by Pradhap P Thursday, July 12, 2018 3:00 PM modified
    Thursday, July 12, 2018 2:58 PM

Answers

  • ok so;

    1. I would check your System and Application event logs to ensure there is not an underlying disk related issue and fix it before taking any action

    2. Make a backup copy of the EDB before you do anything

    3. You really have two choice at this point

    A: Run eseutil /P to repair the db however that can take some time and will result in some type of dataloss.  How much depends on what you find in # 1 and also after you do a repair on an EDB you will need to also run isinteg until it reports not fixing any errors so like I said this will take  some time.  Also once done you will need to create a NEW DB and move all the mailboxes from the OLD DB to the NEW since MS will not support a DB once its been repaired so its best practice to move into a new DB, however the main problem here is you have more downtime for users

    B: the other option would be to do a dial tone restore following this article here, https://support.lucid8.com/support/solutions/articles/6000167684-dial-tone-recovery this will get you up and running immediately and then you just need to either use DigiScope to open the offline copies of the EDB and restore to the production server OR fix the offline EDB's and use the RDB restoring method


    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:32 AM
    • Unmarked as answer by Pradhap P Saturday, July 14, 2018 5:32 AM
    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:33 AM
    Thursday, July 12, 2018 3:18 PM
  • Well that depends on

    1. Check the System Event logs for any disk related issues because if they exists you want to fix those first otherwise things are going to get worse

    2. Also check the application event logs to see if there are any DB's with issues are being reported because again you want to ensure that nothing bad is lurking to take you down again

    1-2.A:  for both of the above filter the event logs to only show critical and error events since those are the ones your really concerned with and anything that is disk or DB related report back and I can give you feedback

    3.  Running eseutil /P and the integrity check on a DB is very disk intensive and it will effect the I/O on the drives and therefore it will impact the other mounted DB's, just how much it effects them will depend on the hardware

    4. run eseutil /MH against the DBs that wont mount to see what it has to say about the DB health and attach that info to the case.  The above you can do without concern because its just a header dump.  Depending on the results we can discuss next actions


    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:32 AM
    Thursday, July 12, 2018 3:38 PM
  • Thanks for your response,

    some databases are working fine.

    if I start the repairing or anything it will affect live.

    few database locations are the same disk & also the same partition.



    Regards, Pradhap P

    The error message indicates that the log files is missing for some reasons, if the log files are inconsistent and there is no backup, we should use /p switch to repair the database.

    Run the eseutil /p and specify the edb file location in the command it will repair the specified database:

    eseutil /p "<database path\DB.edb>"

    Then run eseutil /mh to check the state of the database, if it is Clean Shutdown, run with the /d switch to execute offline defragmentation.

    eseutil /d "<database path\DB.edb>"


    Hope it helps.

    Regards,

    Manu Meng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 13, 2018 7:55 AM
    Moderator
  • Dear Team,

    please help us, for the next action.



    Regards, Pradhap P

    Temporarily move all the log files from the Transaction logs folder location to another drive and then mount the database.

    Regards,

    Manu Meng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 13, 2018 9:52 AM
    Moderator
  • Manu is correct for each DB I would

    1. Take the DBs that are online now and dismount them

    2. Move all LOG and associated files to an alternate location, i.e. you should only have the EDB's in place

    3. Mount the databases and you should be good to go


    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:31 AM
    Friday, July 13, 2018 12:52 PM
  • Dear Team,

    Thanks for your Valuable support.

    Our issue is resolved & successfully mounted.

    -------------------------------------------------------

    Before do anything take backup of database file.

    ----------------------------------
    To check the status:-
    eseutil /MH "<database path\DB.edb>"
    ---------------------------------------------
    To check the output - State: Dirty Shutdown
    if "Dirty Shutdown" start to run repair
    --------------------------------------------
    Repair:-
    eseutil /p "<database path\DB.edb>"
    ---------------------------------------------
    To check the status:-
    eseutil /MH "<database path\DB.edb>"
    To check the output - State: Clean Shutdown
    if "Clean Shutdown" start to run Offline defragmentation
    --------------------------------------------
    Offline defragmentation:-
    eseutil /d "<database path\DB.edb>"
    ---------------------------------------------
    after if any other database is live, that also same  Transaction logs folder location.
    take down time, dismount all database, then move all only log files (.log) to other folder(this is for backup).
    Note: If another database live but different Transaction logs folder location - not required dismount or down.
    ---------------------------------------------
    To Mount the Database:-
    Mount-Database -Identity "<Database identity name>"
    ----------------------------------------------------



    Regards, Pradhap P

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:31 AM
    Saturday, July 14, 2018 5:31 AM

All replies

  • ok so;

    1. I would check your System and Application event logs to ensure there is not an underlying disk related issue and fix it before taking any action

    2. Make a backup copy of the EDB before you do anything

    3. You really have two choice at this point

    A: Run eseutil /P to repair the db however that can take some time and will result in some type of dataloss.  How much depends on what you find in # 1 and also after you do a repair on an EDB you will need to also run isinteg until it reports not fixing any errors so like I said this will take  some time.  Also once done you will need to create a NEW DB and move all the mailboxes from the OLD DB to the NEW since MS will not support a DB once its been repaired so its best practice to move into a new DB, however the main problem here is you have more downtime for users

    B: the other option would be to do a dial tone restore following this article here, https://support.lucid8.com/support/solutions/articles/6000167684-dial-tone-recovery this will get you up and running immediately and then you just need to either use DigiScope to open the offline copies of the EDB and restore to the production server OR fix the offline EDB's and use the RDB restoring method


    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:32 AM
    • Unmarked as answer by Pradhap P Saturday, July 14, 2018 5:32 AM
    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:33 AM
    Thursday, July 12, 2018 3:18 PM
  • Thanks for your response,

    some databases are working fine.

    if I start the repairing or anything it will affect live.

    few database locations are the same disk & also the same partition.



    Regards, Pradhap P

    Thursday, July 12, 2018 3:28 PM
  • Well that depends on

    1. Check the System Event logs for any disk related issues because if they exists you want to fix those first otherwise things are going to get worse

    2. Also check the application event logs to see if there are any DB's with issues are being reported because again you want to ensure that nothing bad is lurking to take you down again

    1-2.A:  for both of the above filter the event logs to only show critical and error events since those are the ones your really concerned with and anything that is disk or DB related report back and I can give you feedback

    3.  Running eseutil /P and the integrity check on a DB is very disk intensive and it will effect the I/O on the drives and therefore it will impact the other mounted DB's, just how much it effects them will depend on the hardware

    4. run eseutil /MH against the DBs that wont mount to see what it has to say about the DB health and attach that info to the case.  The above you can do without concern because its just a header dump.  Depending on the results we can discuss next actions


    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:32 AM
    Thursday, July 12, 2018 3:38 PM
  • Thanks for your response,

    some databases are working fine.

    if I start the repairing or anything it will affect live.

    few database locations are the same disk & also the same partition.



    Regards, Pradhap P

    The error message indicates that the log files is missing for some reasons, if the log files are inconsistent and there is no backup, we should use /p switch to repair the database.

    Run the eseutil /p and specify the edb file location in the command it will repair the specified database:

    eseutil /p "<database path\DB.edb>"

    Then run eseutil /mh to check the state of the database, if it is Clean Shutdown, run with the /d switch to execute offline defragmentation.

    eseutil /d "<database path\DB.edb>"


    Hope it helps.

    Regards,

    Manu Meng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 13, 2018 7:55 AM
    Moderator
  • Thanks for the response.

    eseutil /p "<database path\DB.edb>"
    eseutil /d "<database path\DB.edb>"

    then we will try to mount the database.  

    we will do & update ...

    surely it will not affect another database?


    Regards, Pradhap P

    Friday, July 13, 2018 8:18 AM
  • Thanks for the response.

    eseutil /p "<database path\DB.edb>"
    eseutil /d "<database path\DB.edb>"

    then we will try to mount the database.  

    we will do & update ...

    surely it will not affect another database?


    Regards, Pradhap P

    Yes, it will not affect other databases.

    Regards,

    Manu Meng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 13, 2018 8:25 AM
    Moderator
  • Dear Team,

    after repair

    Status: Clean Shutdown

    offline defragmentation completed.

    after try to mount the database.

    getting the same error.

    -----------------------

    At least one committed transaction log file is missing. Mounting this database
    will result in data loss. Do not take this action unless you cannot locate the
    missing log files. Are you sure you want to continue?
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help
    (default is "Y"):y
    Mount-Database: Exchange is unable to mount the database that you specified. Specified database: KKMAIL\A\4; Error code: MapiExceptionJetErrorRequiredLogFile
    sMissing: Unable to mount database. (hr=0x80004005, ec=-543)

    ---------------------


    Regards, Pradhap P

    Friday, July 13, 2018 9:16 AM
  • Dear Team,

    please help us, for the next action.



    Regards, Pradhap P

    Friday, July 13, 2018 9:46 AM
  • Dear Team,

    please help us, for the next action.



    Regards, Pradhap P

    Temporarily move all the log files from the Transaction logs folder location to another drive and then mount the database.

    Regards,

    Manu Meng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 13, 2018 9:52 AM
    Moderator
  • Other Databases are live. 

    if any possibility to create a new database & restore from edp.


    Regards, Pradhap P

    Friday, July 13, 2018 9:59 AM
  • Manu is correct for each DB I would

    1. Take the DBs that are online now and dismount them

    2. Move all LOG and associated files to an alternate location, i.e. you should only have the EDB's in place

    3. Mount the databases and you should be good to go


    Search, Recover, Export Mailboxes, Folders, Email, Contacts, Calendars, Tasks, etc. from Offline Exchange Databases (EDBs), On-Premise Exchange Servers and Office 365. Migrate/Recover direct from any offline EDB into any On-Premises Exchange Server, even cross version i.e. 2003 → 2007 → 2010 →2013 → 2016 → Office 365 with Lucid8's DigiScope

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:31 AM
    Friday, July 13, 2018 12:52 PM
  • Dear Team,

    Thanks for your Valuable support.

    Our issue is resolved & successfully mounted.

    -------------------------------------------------------

    Before do anything take backup of database file.

    ----------------------------------
    To check the status:-
    eseutil /MH "<database path\DB.edb>"
    ---------------------------------------------
    To check the output - State: Dirty Shutdown
    if "Dirty Shutdown" start to run repair
    --------------------------------------------
    Repair:-
    eseutil /p "<database path\DB.edb>"
    ---------------------------------------------
    To check the status:-
    eseutil /MH "<database path\DB.edb>"
    To check the output - State: Clean Shutdown
    if "Clean Shutdown" start to run Offline defragmentation
    --------------------------------------------
    Offline defragmentation:-
    eseutil /d "<database path\DB.edb>"
    ---------------------------------------------
    after if any other database is live, that also same  Transaction logs folder location.
    take down time, dismount all database, then move all only log files (.log) to other folder(this is for backup).
    Note: If another database live but different Transaction logs folder location - not required dismount or down.
    ---------------------------------------------
    To Mount the Database:-
    Mount-Database -Identity "<Database identity name>"
    ----------------------------------------------------



    Regards, Pradhap P

    • Marked as answer by Pradhap P Saturday, July 14, 2018 5:31 AM
    Saturday, July 14, 2018 5:31 AM