Mountability Check Fails with Jet Error Code 1022 or 1018 (4036084)

Mountability Check Fails with Jet Error Code 1022 or 1018

The following error appears when performing a mountability check.

Mountability Check Failed Exception: Mail store ‘C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0000241996\Mailbox Database 0000241996.edb’ is not mountable. Error: ‘Error opening database. Jet returned error code -1022, Error closing database, Error opening database. Jet returned error code -501, Database cannot be mounted’

* Mountability Check Error Exception: Mandatory database file was not found at the specified destination: C:\ProgramData\AppRecovery\MountPoints\9f2049a2-1e09-4433-aaf0-6e721517a8de\C__\Program Files\Microsoft\Exchange Server\V14\Mailbox\Public\Public.edb

Windows Registry Disclaimer:

Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.

To resolve this issue, complete the following steps.

1. Open the affected Core.
2. Suspend all transfers. --https://support.quest.com/appassure/kb/117991
3. Allow all running/current Exchange mountability checks to complete.
4. Ensure all mounts are dismounted.
5. Stop the Core Service. -- How To Stop or restart the Core Service (4034348) (quest.com)
6. Stop the AAVDisk and AA VStor drivers.
7. Extend the AAVDisk and AAVStor driver NetworkTimeout to 1800 (dec). These values are located at HKLM\SYSTEM\CurrentControlSet\Services\AAVdisk\Parameters\ and HKLM\SYSTEM\CurrentControlSet\Services\AAVStor\Parameters\.
8. Extend the AAVDisk and AAVStor driver AsyncNetworkTimeout to 1800 (dec). These values are located at HKLM\SYSTEM\CurrentControlSet\Services\AAVdisk\Parameters\ and HKLM\SYSTEM\CurrentControlSet\Services\AAVStor\Parameters\.

Note: If AsyncNetworkTimeout key does not exist. Create a DWORD 32 with the name AsyncNetworkTimeout in the Parameters folder. 

1. Start the AAVDisk and AAVStore drivers.
2. If the drivers start, restart the Core Service and resume transfers.
3. If the drivers do not start, reboot the Core server.
4. After the reboot, start the Core Service and resume transfers.
5. Go to the Configuration tab, Settings, Replay Engine timeout
6. Increase the timeout to 5 or 10 minutes

To start and stop the AAVDisk:

1. Run the cmd as administrator
2. Enter one of the following commands:
   1. sc stop aavdisk
   2. sc start aavdisk

Note: If these steps do not resolve the issue, check the original database for additional errors using eseutil