| Event Id | 1115 |
| Source | MSExchangeIS Mailbox Store |
| Description | Error 0xfffffae2 returned from closing database table, called from function JTAB_BASE::EcCloseTable on table 1-F9F30. |
| Event Information | As per Article MS312966: This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3. For more information see reference link MS312966. As per Article MS970671: Cause: This issue occurs because once the database resources reach the timeout value they go into a failed state. Once this occurs the waiting dependent resources such as physical disk are brought offline by cluster and the errors are seen. Resolution: It is possible to eliminate these events by increasing the timeout on the database resources. Increasing the timeout can give the DBs more time to go down cleanly, avoiding the ESE errors. The default timeout is 180 seconds. Increasing the timeout, does increase the time it takes to failover. The timeout will typically be customer specific. Typically, for most clusters a timeout value of 5 minutes (300 seconds) should alleviate the problem. The value is set with the following command: cluster res " This can also be set in Cluster Administrator on the properties of the database resource(s) on the advanced tab, changing pending timeout to the desired value. For more information see reference link MS970671. According to Microsoft: This event indicates a problem with the database. The error code will give an indication of the underlying problem. You can use the ERROR.EXE program on the Exchange Server CD to decode the error code. For example, error 0xfffffbbe maps to JET_errInstanceUnavailable. Similarly, error 0xfffffae2 maps to JET_errInvalidTableId. Other related events preceding or succeeding this event may also provide an indication of the underlying problem. Depending on the error code, the exact cause of corruption may or may not be determinable. User Action: Check the application log for related events. Make sure that the latest service pack for Exchange Server has been applied. The context is very important in troubleshooting this error (and other similar errors). For example, if a third-party application, such as an antivirus scanner, has recently been installed and the problem appears soon after that, you need to investigate if there are known issues with the antivirus software and/or if the vendor of that software has released a hotfix (or hotfixes) to resolve the issue. |
| Reference Links | MS970671 MS312966 This event indicates a problem with the database XADM: The Information Store Generates a 0xfffffae2 JET_errInvalidTableId Error During Many Client Operations |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.