Information Store Does Not Mount with 0xfffff745 and -2235 Errors
This article applies to…
This article was previously published under Q307242

SYMPTOMS
An information store database may not mount and you may receive the following error message in Exchange System Manager:

An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: c1041724
The following error messages are logged in the Application event log:

Event Type: Error
Event Source: ESE98
Event Category: Database Corruption
Event ID: 470
Description: Information Store (1892) Database C:\Exchsrvr\mdbdata\priv1.edb is partially attached. Attachment stage: 4. Error: -2235.

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description: Error 0xfffff745 starting database "First Storage Group\Mailbox Store (MAIL1)" on the Microsoft Exchange Information Store. Failed to attach to Jet DB.

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Description: Error 0xfffff745 starting Storage Group /DC=COM/DC=COMPANY/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=MICROSOFT/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=MAIL1/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store. MDB failed to start.

CAUSE
This issue can occur if Exchange cannot create and access files in the folder that the TMP system environment variable specifies. This issue can also occur if Exchange does not have full control from the root of the drive down to the transaction logs and databases.

RESOLUTION
To resolve this issue, double-click the System icon in Control Panel, click the Advanced tab, and then click Environment Variables. In the lower pane, locate the TMP (not TEMP) variable under System Variables. The path that is specified (C:\Winnt\Temp by default, usually the same path for both the TMP and TEMP variables) is the folder that Exchange must be able to access by using the system account. Grant the Administrators group or the system account Full Control permissions. Granting permissions to the Domain Admins group is not sufficient.

If permissions to the TMP folder are correct, check the permissions on each drive that contains the databases or logs. The system account must have full control at the root of the drive and at each folder that contains Exchange databases or transaction logs. For example, if you have transaction logs in C:\Exchsrvr\Mdbdata, the system account needs full control on the root of C: on the Exchsrvr folder and on the Mdbdata folder for the databases to mount.

MORE INFORMATION
The -2235 and 0xfffff745 errors in the error messages in the "Symptoms" section of this article are equivalent terms. These errors are also equivalent to the Extensible Storage Engine (ESE) error message JET_errSLVFileAccessDenied, which means "Cannot access SLV File, the SLV File is locked or is in use."

Note: An SLV file is a super-long value file, which is known as an .stm Exchange database file (for example, Priv1.stm or Pub1.stm).

For additional information about ESE codes, click the article number below to view the article in the Microsoft Knowledge Base:
266361 XADM: Extensible Storage Engine 98 Error Codes 0 to -1048

266367 XADM: Extensible Storage Engine 98 Error Codes -1051 to -999999

The information in this article applies to:
Microsoft Exchange Server 2003 Enterprise Edition
Microsoft Exchange Server 2003 Standard Edition
Microsoft Exchange 2000 Server