Tested Solutions For Microsoft Exchange Data Store Error 1053 on Startup
Note: The Exchange Information Store was discontinued after the release of Exchange Server 2013. Managed Store is now tied to Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe processes.
Microsoft Information store is responsible for managing so many types of information within an Exchange Server. The main components of Exchange Information Store are Mailbox Database and Public Folder Database.
There are various reasons for the Information Store corruption. Some of them are listed below:
- Unexpected system shutdown.
- Data being incorrectly written to the disk etc.
- Using of Third Party Antivirus and Backup software cause corruption of Exchange Information Store.
- Exchange information store database transaction log drive becomes full.
- The corruption of database files may be caused by hardware problems.
- When the database reaches its size limit
Problem : Microsoft Exchange Information Store Error
“Could not start the Microsoft Exchange Information Store service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion.”
Possible Causes for Information Store Error 1053
- Incompatible .NET Framework: One reason behind the Microsoft Information store Error 1053 code is due to incompatible .NET framework Installation against the service pack for Exchange Server.
- The jcb.dll file in callback library is missing or corrupt.
- Improper synchronization or connection between the following groups: (a) MS-Exchange Server (2) MS-Information Store (3) System Attendant Service
Solution
To resolve the Error: 1053 you need to download the latest version of .NET framework (according to your Exchange Server Edition). If the issue is because of jcb.dll file corruption then you need to copy jcb.dll file from Exchange Server 2003 SP2 to installation disc to “Exchsrvr/bin” folder.
Other steps that you can follow in order to solve the Microsoft Exchange Information Store Error code: 1053 are mentioned below:
- Open the Windows Server Event Viewer and check the log for the following services: EDB file, MS ExchangeIS, MS ExchangePriv, MS ExchangePub.
- Shut down all the running Exchange Services and reboot the system. When Information Store starts it will try to restore the database in consistent state.
- You can also try taking the full online backup which contains EDB, STM and LOG files. And restore database
If the above-mentioned methods fail to repair Exchange Information Store then the last option left is to wipe off the information store. But this will cause losing of important data files. So, it is recommended to Recover EDB data first using EDB Repair Tool and then perform the wipe operation.