Read time 2 minutes

Microsoft Exchange Server saves mailbox store and public folder store in a repository called information store service. Sometimes, when you try to start the information store service, Exchange Server generates the following error message:

The Microsoft Exchange Information Store service terminated with service specific error 4294966277.

The preceding error message states that there is some problem in the initialization of information store service. However, detailed information about the preceding error message is recorded in various events in Application log and System log:

Events recorded in application log

Event ID: 0

Source: ESE97
Type: Error
Category: Logging/Recovery
Description: MSExchangeIS ((451)) -1019

Event ID: 1120

Source: MSExchangeIS
Type: Error
Category: General
Description: Error 0xfffffc05 initializing the Microsoft Exchange Server Information Store database.

Event recorded in system log

Event ID: 7024

Source: Service Control Manager
Type: Error

Description: The Microsoft Exchange Information Store service terminated with service-specific error 4294966277.


The specified error message is generated when a blank page is found in Exchange Server database. This error message can also be generated when an important page in the database gets corrupt. You cannot even repair corrupt Exchange database using eseutil.exe utility to resolve this error message. When you try to use eseutil.exe to get rid of this particular error message, following error message will be generated:

1019 0xFFFFFC05 JET_errPageNotInitialized Repair Only: Read and  unused page  4294966277

The preceding error message indicates the database corruption. Therefore, you need to restore the database from backup to reuse it.


Following steps help you to resolve the JET_errPageNotInitialized error message:

  • Create offline backup of the Exchange Server database including all transaction logs.
  • Include EDB.chk file in backup.
  • Disable all virus programs.
  • Examine system logs to confirm that there is no hardware related errors.
  • Include all Application and System logs in backup set.
  • Verify that all hardware on the machine where Exchange Server is installed are properly configured and working.
  • Restore the backup.

Apart from restoring the backup, you can also try using Kernel for Exchange Server recovery software. It is specially designed third-party tool to perform EDB file recovery from databases of MS Exchange Server 5.0 to 2016. Users can also download the free trial version of EDB to PST converter software to evaluate its features and functionalities.

Kernel for Exchange Server
Related Posts