Exchange Mountability Checks Fail with JET 1018 and JET 1022 Errors (4034312)

Exchange Mountability Checks fail with JET 1018 and 1022 errors. These errors are usually the result of a lack of resources. For more information, click here. The following steps may help to detect possible reasons that may cause the issue.

• Application Logs: There may be ESE errors that state “The read operation will fail with error -1022 (0xfffffc02)”.  If Exchange asks the operating system for a page in the database and an error occurs instead of the page data being returned, a -1022 error (JET_errDiskIO) results. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database.
• System logs: There may be NTFS errors that state “Ntfs 55; the file system structure on disk is corrupt and unusable. Please run the CHKDSK /R utility on the volume “Drive_letter”.”  The NTFS error is generated as a result of the ESE 1022 error, as Windows believes there is an issue with the disk because it was unable to fulfill a request by an application.
• Mountability Error example: Mail store 'D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 2012043020\Mailbox Database 2012043020.edb' is not mountable. Error: 'Error opening database. Jet returned error code -1018, Error closing database, Error opening database. Jet returned error code -1018, Database cannot be mounted' 

These issues may be the result of insufficient Disk I/O or lack of memory to fulfill the request by AppAssure to mount and check the recovery point in memory.

To resolve the issue complete the following steps. Please note this will require a reboot of the core if AAVDisk cannot be stopped and started.

1. On core Web UI select Tools, click Mounts, and Dismount All mounted recovery points
2. Stop the Core Service How To Stop or restart the Core Service (4034348) (quest.com)
3. Apply Semaphore Timeout changes Error with Core tasks results with, "The semaphore timeout period has expired" (4036274) (quest.com)
4. Start Core Service, resume jobs, and force Mountability Check on latest recovery point