XADM: ESE Will not Retry Operations during ESEUTIL /G (199914)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q199914 SUMMARY
When the Exchange Database Engine encounters a read verification failure, referred to as an -1018 error, (in accordance with Knowledge Base article 151789, XADM: Error -1018 (JET_errReadVerifyFailure)), it will now retry to successfully read the page a maximum of 16 times. This is a new feature of the Exchange Database Engine, referred to as "ESE," and was introduced in build 5.5.2395.0 of Ese.dll.
However, when using ESEUTIL to perform an Integrity Check (ESEUTIL /G), retry operations are not performed if the Exchange Database Engine encounters a read verification failure. If ESE retries to read the page it originally failed on (when running either Repair or Integrity Check), the length of time to run ESEUTIL increases dramatically.
Modification Type: | Minor | Last Reviewed: | 4/21/2005 |
---|
Keywords: | kbinfo KB199914 |
---|
|