Read time 2 minutes

Microsoft Exchange Server stores mailbox and public folder data within a dedicated repository known as the Information Store Service. Occasionally, when attempting to initiate this service, Exchange Server may produce the following error message:

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

The error message above indicates an issue with the initialization of the information store service. However, comprehensive details regarding this error are documented in multiple events within both the Application log and the 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.

Reason of JET_errPageNotInitialized error

The indicated error message arises in situations where an empty page is detected within the Exchange Server database or when a critical page within the database becomes corrupted. Attempting to rectify this error message using the eseutil.exe utility is futile, as it cannot repair corrupt Exchange database to resolve this issue. When attempting to employ eseutil.exe to eliminate this specific error message, you will encounter the following error message:

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

The error message above points to a database corruption issue. Consequently, you must initiate a database restoration from a backup in order to make it operational once more.

Solution to resolve the JET_errPageNotInitialized error

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.

In addition to the conventional backup restoration method, consider exploring Kernel for Exchange Server software as an alternative solution. This specialized third-party tool is meticulously crafted to facilitate EDB file recovery from MS Exchange Server databases spanning from version 5.0 to 2016. To get a firsthand experience of its capabilities and features, users have the option to download a complimentary trial version of the EDB to PST converter software. This allows you to assess its performance and functionalities before making a commitment.

Exchange Recovery tool

Kernel for Exchange Server