Article ID: 242364 - View products that this article applies to.
This article was previously published under Q242364
This article has been archived. It is offered "as is" and will no longer be updated.
After you run an offline defragmentation (the eseutil /d command), the information store does not start and returns an error message 4294966277.
The following events are logged in the application event log:
The Tempdfrg.edb file (this file name may be different if you used a /t switch in the defragmentation command) that is created during the defragmentation is still on the drive; a normal defragmentation deletes it.
Event ID: 0
Description: MSExchangeIS ((451)) -1019
Event ID: 1120
Description: Error 0xfffffc05 initializing the Microsoft Exchange Server Information Store database.
The information store defragmentation does not finish the copy of the database from the temporary (defragmented) file back to the original location. The database is therefore damaged and unusable. The 4294966277 error message is a JET_errPageNotInitialized error, which means that a page within the database is blank or has not been properly initialized.
When the offline defragmentation does not finish the copy, the temporary database is not deleted. If the temporary database is the intact, successfully defragmented database, you can manually copy it back to the correct location.
If you only defragmented one database and already know which database is damaged, proceed to the "Copying the Temporary Database" section of this article. If you defragmented both the Priv.edb and Pub.edb databases and you are not sure which database has caused the problem, perform the following steps to determine which database is causing the problem:
Copying the Temporary DatabaseTo ensure that the database defragmentation finished successfully and to copy the defragmented file back to the correct location:
An offline defragmentation copies data from the current database to a new database file. When the defragmentation process reaches 100% the temporary file is a complete and defragmented database. At this point, the utility copies the temporary file back to the original location, which overwrites the original database.