eseutil /r failed

With referring to http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_28573464.html.

I do encountered another whereby when i try to run eseutl /r, the message: Operation terminated with error -543 (JET_errRequiredLogFilesMissing, The required log files for recovery is missing.)

However the requires are present:

Initiating FILE DUMP mode...
         Database: D:\RSG412\Vol_U\MDB412\mdb412.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,12
 Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:09/13/2010 13:46:10 Rand:242030964 Computer:
         cbDbPage: 8192
           dbtime: 5848828792 (0x15c9e0b78)
            State: Dirty Shutdown
     Log Required: 2501671-2501675 (0x262c27-0x262c2b)

Event viewer:

eseutil (2788) Database D:\RSG412\Vol_U\MDB412\MDB412.edb requires logfiles 2501671-2501675 in order to recover successfully. Recovery could only locate logfiles starting at 2501675.
Log.JPG
LVL 19
suriyaehnopAsked:
Who is Participating?
 
suriyaehnopAuthor Commented:
Problem solved.

eseutil /ml showed that all of the logs were correct. I ended up removing the checkpoint file and eseutil /r ran succesfully

https://social.technet.microsoft.com/Forums/en-US/c1503370-a581-4c8b-90ee-11e05d019b47/cant-bring-db-to-clean-shutdown-state?forum=exchangesvravailabilityandisasterrecovery
0
 
VB ITSSpecialist ConsultantCommented:
If you're missing log files then you can try running the following commands to get repair your database to get it to a working state:
First of all make a backup of the files if this is your only working copy. The below commands may damage your Exchange database beyond repair. Although the risk of this is minimal, it's always good to have a backup - even if it takes an hour or two to transfer them to an external USB drive. It will save your butt if you damage your database and log files.
Run eseutil /p to perform a repair operation on the database.
Run eseutil /d to defragment and rebuild the indexes on the database.
Lastly use isinteg to repair the database and address any corruption.
Remove all log files including checkpoint files then try and mount the database.

Refer to these articles if you need more information on the switches to use with eseutil and isinteg:
eseutil: http://technet.microsoft.com/en-us/library/aa996953(v=exchg.65).aspx
isinteg: http://support.microsoft.com/KB/182081
0
 
suriyaehnopAuthor Commented:
As i mentinoned the require log are there, please see the screenshot and eseutil /mh result.
0
 
suriyaehnopAuthor Commented:
I ended up removing the checkpoint file and eseutil /r ran succesfully.

No point given
0
 
Marshal HubsEmail ConsultantCommented:
Check full steps to repair corrupt Exchange database by using  eseutl /r: https://www.stellarinfo.com/article/repair-exchange-2010-with-eseutil.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.

All Courses

From novice to tech pro — start learning today.