App Asure Replay CoreWith App Assure you may get the following errors after a new install of a Replay Core server and an the agent running on a Exchange 2010 server database.

Error

Thread: 2520

Logger: DsmRpChecker

Context:

Source Location: DsmRecoveryPointChecker.cpp:341

Details:

Mountability check for ‘Mailbox Database 0401075076’ failed: Exchange database engine error: Error closing database

and/or

Error

Thread: 2520

Logger: DsmRpChecker

Context:

Source Location: DsmRecoveryPointChecker.cpp:341

Details:

Mountability check for ‘Mailbox Database 0401075076’ failed: Exchange database engine error: Unable to initialize JET session. See log for details.

 

There is a known issue with Exchange 2010 running on SP1 with RollUps where this problem is experienced.

Please apply the below registry fix to the Replay Core server, and capture a new recovery point (snapshot) from the protected server to resolve the issue. Furthermore, after deployment of this fix you can go back and check the past recovery points that failed and “Force Recovery Point Check” to confirm they are good as well and get the green check symbol assigned to them.

Modify the registry on the Replay Core at the following location and assigned the specified value below:

Navigate to the location: HKEY_LOCAL_MACHINE\SOFTWARE\AppAssure\ReplayDSM\EseConfig

Modify value for “ForceDeleteUnicodeIndex” (type REG_DWORD) and assign a value of 2.

 

I hope this helps some one out there..

Enjoy 😎

Cubert

Tagged with:
 

8 Responses to “App Assure – Replay Core Mountability check for ‘Mailbox Database’ failed: Exchange database engine error: Error closing database”

  1. Mike says:

    I am having this very issue on Small Business Server 2011 with Exchange Server 2010. I have attempted your fix with both hex and decimal 2’s, but I still get the error message hourly (when snapshots are scheduled). Our ticketing system kicks out 5 messages after each backup, so you can imagine how many tickets we have to clear each morning. Any help you could impart would be greatly appreciated.

  2. Bob says:

    Worked for me! Thanks!

  3. Bob says:

    Also there’s no difference between 2 hex and 2 decimal…lol

  4. Vadim says:

    Also worked for me, thanks, didnt find this article on on appassure site.

  5. Tom says:

    Thanks!! Was getting the JET error. No need to create a new snap, force checking was all that was needed.

  6. Anonymous says:

    Thanks it worked for me too.

  7. Kevin says:

    This also worked for me. After not hearing from appassure support for over a week

  8. Jim Kenah says:

    This worked, thank you! I sent the link to the AppAssure tech who was working with me on the issue.

Leave a Reply

*



%d bloggers like this: