MS Exchange Server Event 177 1081 Error Codes

Microsoft Knowledge Base Article - 224977

XADM: Information Store Fails to Start: 4294965882,
FFFFFA7A, Event 177, 1081, and Others

This article was previously published under Q224977

IMPORTANT: This article contains information about modifying the registry. Before you registry, make sure to back it up and make sure that you understand how to restore the problem occurs. For information about how to back up, restore, and edit the registry, click article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry

SYMPTOMS
The Microsoft Exchange Server information store may not start after restoration of an online Information store utilities such as Isinteg and Eseutil also may not start. You may receive following error messages:
Error -1414 or 0xfffffa7a or 4294965882 (JET_errSecondaryIndexCorrupted)
Error -1030 or 0xfffffbfa or 4294966266 or c8000406 or 3355444230 (JET_errAlreadyInitialized)
Error -1032 or 0xfffffbf8 or 4294966264 (JET_errFileAccessDenied)

You may observe some or all of the following clusters of events in the Application Log:

Event ID: 172
Description: MSExchangeIS ((pid) ) The database engine is initiating index cleanup '<DATABASE.EDB>' as a result of an NT version upgrade from <version> to <version>.
Event ID: 177
Description:MSExchangeIS ((pid) ) Database '<DATABASE.EDB>': The secondary index NUMBER>' of table '<TABLE>' is corrupt. Please defragment the database to rebuild Event ID: 1081
Description: Unable to recover the database because error 0xfffffa7a occurred after Event ID: 5000
Description: Unable to initialize the Microsoft Exchange Information Store service. Error . . . . .
Event ID: 1080
Description: Unable to recover the database because error 0xc8000406 occurred after operation. The database was already called.
Event ID: 5000
Description: Unable to initialize the Microsoft Exchange Information Store service. Error . . . . .
Event ID: 1081
Description: Unable to recover the database because error 0xfffffbfa occurred after Event ID: 5000
Description: Unable to initialize the Microsoft Exchange Information Store service. Error . . . . .
Event ID: 145
Description: MSExchangeIS ((pid) ) The database engine could not access the file called
<path>\edb.log.
Event ID: 1120
Description: Error 0xfffffbf8 initializing the Microsoft Exchange Server Information Store Event ID: 5000
Description: Unable to initialize the Microsoft Exchange Information Store service. Error

CAUSE
When the service pack level for Windows NT changes, Exchange Server rebuilds its database precaution against incompatibilities with the service pack. This reindexing occurs whether level is changed upward or downward.
In most cases, the index rebuild is virtually transparent and goes unnoticed. But if the also been changed along with the service pack level, the above symptoms may appear. case in which this happens is during restoration of an online backup during single mailbox procedures undertaken on a laboratory server.
To have consistent success with Exchange online restores, always target the Exchange a recovery computer running the same Microsoft Windows NT Service Pack as the computer taken from. For example, if the Exchange 5.5 server you backed up was running Windows recovery server must also run Windows NT 4.0 SP5.
These symptoms may also appear when no service pack revision has occurred, but computer changed, if both computers are running Windows NT 4.0 Service Pack 4.

RESOLUTION
IMPORTANT: Please read the entire "Resolution" section before proceeding. The steps procedure are listed below.

This problem can be resolved by any one of the following three methods:
Performing an offline defragmentation of the database (ESEUTIL /D
Giving the current server the same name as the server from which the backup was
may be inconvenient, as two servers with the same name cannot co-exist on the same l Following the procedure outlined below:IMPORTANT: Perform the following steps omitting none of them. While some steps may seem redundant, each one plays a vital successfully reindexing and avoiding the necessity to defragment the database or rename WARNING: If you use Registry Editor incorrectly, you may cause serious problems you to reinstall your operating system. Microsoft cannot guarantee that you can solve result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. After online restore, start the information store.
NOTE: After restoration of an online backup, the first thing you should always case, is to start the associated database service. Running Eseutil or Isinteg, or with any of the restored files or registry entries before starting the database service database permanently unstartable and require another restoration of your full backup.
2. Start Regedt32, and then locate the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\in Progress
Make sure that the "EDB Database recovered" value is 01, not 00. If this value critical parts of the restore process have finished (specifically, the restored .pat applied to the database) and it is safe now to remove the Restore in Progress
If the flag is 01, save, and then delete the Restore in Progress key. If it is still discover the cause before deleting the key.
In the case of the symptoms described in this article, stopping ALL Exchange Server including the System Attendant, and then restarting the database service sets the there are complicating unrelated factors present. Verify that all services have actually typing net start at a command prompt.
IMPORTANT: If the flag is 00 at this step, you must stop all services, restart the and then recheck the key before proceeding to the next step, despite the fact that seem redundant, and even though the database service will likely fail the next anyway.
3. Stop ALL Exchange Server services. Verify that all services have actually stopped at a command prompt.
4. Start the database service. It should fail with a 1011 error, indicating that you database. Patching is a normal operation that does not imply or suggest any damage If you do not receive a 1011 or other event telling you to patch the database, you troubleshoot the failure before proceeding to the next step.
5. Run Isinteg -patch.
6. Start the database service.

The information in this article applies to:
Microsoft Exchange Server 5.0
Microsoft Exchange Server 5.5

Last Reviewed: 5/14/2003 (2.0)
Keywords: kbprb KB224977