Microsoft KB Archive/307242

= Information store does not mount with 0xfffff745 and -2235 errors =

Article ID: 307242

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



This article was previously published under Q307242





SYMPTOMS
When you start a computer that is running Microsoft Exchange2000 Server or Microsoft Exchange Server 2003, or when you try to create a blank Exchange database, all the information store databases may not mount successfully, 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

Date:

Time:

Computer:

Description: Information Store (1892) Database \mdbdata\priv1.edb is partially attached. Attachment stage: 4. Error: -2235.

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 9519

Date:

Time:

Computer:

Description: Error 0xfffff745 starting database &quot;First Storage Group\Mailbox Store &quot; on the Microsoft Exchange Information Store. Failed to attach to Jet DB.

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 9518

Date:

Time:

Computer:

Description: Error 0xfffff745 starting Storage Group /DC= /DC= /CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=MICROSOFT/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN= /CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store. MDB failed to start.

If you are using Microsoft Exchange 2000 Server Service Pack 2 or later, event source ESE98 is replaced by event source ESE. Additionally, the 0xfffff745 value may also be represented by the 0xfffff743 value. In this case, event ID 470 contains error -2237 instead of error -2235, and you may also see the following event before the other events:

Event Type: Error

Event Source: ESE

Event Category: Performance

Event ID: 0

Date:

Time:

Computer:

Description: Information Store (3096) Unexpected Win32 error: 267L



CAUSE
This issue occurs if Exchange cannot create or access the files in the folder that the TMP system environment variable specifies. For example, this issue occurs if the TMP environment variable is mapped to a remote drive or to a storage area network (SAN), and that mapped drive or SAN is no longer available. This issue can also occur if Exchange does not have full control permissions from the root of the drive down to the transaction logs and databases. This issue can also be caused by an incorrect registry setting regarding the TMP or TEMP environment variable.



RESOLUTION
To resolve this issue, verify that both the TMP environment variable and the TEMP environment variable point to a valid location in Windows. To do this, follow these steps:

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
 * 1) Click Start point to Settings, and then click Control Panel.
 * 2) Double-click System, click the Advanced tab, and then click Environment Variables.
 * 3) Under System variables, click TEMP, and then click Edit.
 * 4) If a valid path does not appear in the Variable Value box, type a valid path for the TEMP variable, and then click OK. For example, type %systemroot%\Temp, and then click OK.
 * 5) Under System variables, click TMP, and then click Edit.
 * 6) If a valid path does not appear in the Variable Value box, type a valid path for the TMP variable, and then click OK. For example, type %systemroot%\Temp, and then click OK.
 * 7) Click OK two times to close the System Properties dialog box.
 * 8) Restart the computer.

By default, the following path is specified for both the TMP and the TEMP system environment variables:

%SYSTEMROOT%\Temp

Exchange must access this folder location by using the SYSTEM account. You must assign the local Administrators group or the SYSTEM account Full Control permissions to the Temp folder. It is not sufficient to assign Full Control permissions to the Domain Admins group. To view these permissions:
 * 1) Right-click Start, and then click Explore.
 * 2) Right-click the Temp folder that is specified in your system environment variable, and then click Properties. Typically, this is %systemroot%\Temp.
 * 3) Click the Security tab.
 * 4) In the Name list, click SYSTEM, and then view the assigned permissions that appear in the Permissions list.

If permissions to the Temp folder are correct, verify the permissions on each drive that contains the Exchange database files or the Exchange log files. The SYSTEM account must have Full Control permissions at the root of the drive and at each folder that contains Exchange database files or the Exchange transaction log files. For example, if you have transaction logs in the C:\Exchsrvr\Mdbdata folder, the SYSTEM account must have Full Control permissions to the root directory of drive C, to the Exchsrvr folder, and to the Mdbdata folder.

To determine whether the problem is caused by incorrect registry settings, follow these steps:  Click Start, click Run, type in Regedt32.exe, and then click OK. Locate the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

 Locate the TMP (or TEMP) name in the right pane. This key should be of the REG_EXPAND_SZ type. If either of the keys is incorrect, back up the Environment subkey and then delete the TMP and/or TEMP value on the right. Click Start, then click Run, type in Sysdm.cpl, and then click OK. On the Advanced tab, click Environment Variables.</li> In the System variables list, verify that the value(s) you deleted in step 4 is not present in the list.

Note You may have to scroll down to see the TEMP / TMP variables.</li> Click New. In the Variable Name box, type the names that you deleted in step 4. For example, type C:\Winnt\TEMP.</li> Click OK three times, and then restart the computer.</li></ol>

<div class="moreinformation_section">

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

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

For additional information about ESE codes, click the following article number to view the article in the Microsoft Knowledge Base:

266361 Extensible Storage Engine 98 error codes 0 to -1048

266367 Extensible Storage Engine 98 error codes -1051 to -999999

Additional query words: reviewdocid XADM

Keywords: kberrmsg kbprb KB307242

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.