Microsoft KB Archive/327904

Knowledge Base

XADM: Information Store Does Not Function Correctly If Information Store Transaction Log Reaches Edbfffff.log

Article ID: 327904

Article Last Modified on 10/27/2006

---

APPLIES TO

• Microsoft Exchange Server 5.5 Standard Edition

---

This article was previously published under Q327904

SYMPTOMS

When the Exchange 5.5 server information store transaction logs reach the maximum log file name sequence of Edbfffff.log, you may experience one or more of the following symptoms:

• The information store may stop unexpectedly.
• The information store may not work correctly.
• You may receive the following event entry in the Event Viewer Application Log:

  Event ID: 125
  Event Source: ESE97
  Event Type: Error
  Description:
  MSExchangeIS () Unable to create the log. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -519.

• You may not be able to start the information store. After you try to do so, you may receive the following event entry in the Event Viewer Application Log:

  Event ID: 7024
  Event Source: Service Control Manager
  Event Type: Error
  Description:
  The Microsoft Exchange Information Store service terminated with service-specific error 4294966786.

RESOLUTION

To resolve this issue, use one of the following methods.

Method 1

Restore the information store databases from tape backup. For additional information about offline information store backup procedures for Exchange Server, click the article numbers below to view the articles in the Microsoft Knowledge Base:

296787 XADM: Offline Backup and Restore Procedures for Exchange Server 4.0, 5.0, and 5.5

183266 XADM: How to Restore an Offline Backup of the Directory Service and Information Store

Method 2

Use the Eseutil.exe utility to perform a hard repair of the information store databases. For more information about how to perform a hard repair of the information store databases, click the following article numbers to view the articles in the Microsoft Knowledge Base:

259851 Ramifications of running the eseutil /p or edbutil /d /r command in Exchange

182903 XADM: ESEUTIL Command Line Parameters

261947 XADM: How to Determine if Hard Repair (Eseutil /p) Has Been Run on a Database

WORKAROUND

To prevent this issue, occasionally monitor the transaction logs. Note when the name of the log file approaches 0xfffff, for example, Edbfffff.log. When the name of the log file approaches 0xfffff, reset the log file name sequence to Edb.log:

1. Stop all Exchange Server services that are running on the computer:
   1. Click Start, point to Settings, and then click Control Panel.
   2. Double-click Services.
   3. In the Service box, click each Exchange service that is running on the computer, and then click Stop.
   4. Click Yes when you are prompted to confirm the action.
   5. Click Close.
2. Use the Eseutil.exe utility to dump the header of the Exchange database files and verify that the databases are in a clean shutdown state:
   1. Click Start, and then click Run.
   2. Type cmd, and then click OK.
   3. Type eseutil /mh path to the Exchange Server database file | more , and then press ENTER. For example, to dump the header of the private information store database file C:\Exchsrvr\Mdbdata\Priv.edb, type eseutil /mh c: exchsrvr\mdbdata\priv.edb | more at the command prompt, and then press ENTER.
   4. The following message indicates that the database is in a clean shutdown state:

      State: Consistent

3. Delete the transaction logs and the checkpoint file:
   1. Use Windows Explorer to open the drive letter:\Exchsrvr\Mdbdata folder.
   2. Delete each of the following files, where xxxxx is a string of hexadecimal numbers:

      Edb.log
      Edbxxxxx.log
      Edb.chk

   3. Click Yes when you are prompted to confirm the deletion.
   4. Quit Windows Explorer.
4. Start the Exchange Server services that you previously stopped:
   1. Click Start, point to Settings, and then click Control Panel.
   2. Double-click Services.
   3. In the Service box, click the Exchange service that you want to start, and then click Start.
   4. Click Yes when you are prompted to confirm the action.
   5. Click Close.

MORE INFORMATION

For additional information about how to troubleshoot information store startup issues, click the article number below to view the article in the Microsoft Knowledge Base:

147244 XADM: Troubleshooting Information Store Startup Problems

For additional information about the Eseutil utility, click the article numbers below to view the articles in the Microsoft Knowledge Base:

170091 XADM: Location of the Eseutil Utility

182903 XADM: ESEUTIL Command Line Parameters

183888 XADM: Free Disk Space Requirements for Eseutil.exe

Keywords: kbenv kberrmsg kbprb KB327904

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.