The information store is dismounted, and an event ID 1159 message is logged in Exchange Server 2003 or in Exchange 2000 Server

In Microsoft Exchange Server 2003 or in Microsoft Exchange 2000 Server, the information store is dismounted. Additionally, an event that is similar to the following event is logged in the Application log on a server that is running Exchange Server 2003 or Exchange 2000 Server:

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 1159
Description: Database error 0xfffffd9a occurred in function JTAB_BASE::EcUpdate while accessing the database "<DatabaseName>".

Note The error code 0xfffffd9a translates to JET_errCheckpointDepthTooDeep.

This issue occurs if the storage group that is related to the information store contains more than 1008 uncommitted Extensible Storage Engine (ESE) transaction log files. Each ESE storage group has a hard-coded limit of 1024 uncommitted ESE transaction log files. When the number of uncommitted ESE transaction log files in an ESE storage group reaches 1008, Exchange Server 2003 or Exchange 2000 Server starts to dismount all the information stores in the storage group. Additionally, the event ID 1159 message is logged in the Application log.

To resolve this issue, restart the Microsoft Exchange Information Store service. To do this, follow these steps on the server that is running Exchange Server 2003 or Exchange 2000 Server:

1. Click Start, click Run, type services.msc, and then click OK.
2. Click Microsoft Exchange Information Store Service, and then click Restart Service.
3. Quit the Services tool.

This behavior is by design.

Many uncommitted ESE transaction log files may be created in any one of the following scenarios:

• A process is locked in the backup software that you are using. Or, the backup software has stopped responding.
• You may be performing large-scale mailbox moves at the same time that a backup process is occurring. To work around this issue, perform one task at a time.
• The server may be experiencing performance issues. For example, disk subsystem issues may prevent the server from responding quickly to simultaneous disk-intensive operations.

To determine how many uncommitted ESE transaction log files are in the storage group, review the checkpoint depth. The checkpoint depth is the difference between the location of the checkpoint file and the location of the E0x.log file. The checkpoint file lists transactions that have been committed to the database. The checkpoint depth indicates how many ESE transaction log files contain content that has not yet been committed to the information store.

For more information about how to monitor the number of uncommitted ESE transaction log files that are contained in a particular storage group, click the following article number to view the article in the Microsoft Knowledge Base: