The Exchange Information Store is a critical server component which, if facing issues, can put the entire lot of server activities on hold. Errors like 1053 on startup can be especially problematic since they can lead to complete inaccessibility of user mailboxes and public folder databases which are parts of the Information Store. Stellar Phoenix Mailbox Exchange Recovery software is a product that can prove to be a worthy asset when trying to combat errors like this.
Introduced in Exchange 2000, the Information Store is primarily composed of mailbox and public folder databases. Exchange Information Store (IS) is a storage platform that is used to manage different types of information within Exchange server. Storage Groups are a critical component of the IS and are comprised of multiple public and private stores. It is in these public and private stores that the actual Exchange databases reside. Depending upon their type, various database components are saved within EDB and STM files. The rich text MAPI database gets saved in EDB file while STM files store streaming data along with the content that arrives from the SMTP source.
Since the health of the IS directly impacts how Exchange server works, even minor issues within it can lead to disasters. Citing the case of one of our clients here, following an Exchange server system update, they constantly faced issues where the IS would not start like it should automatically but instead, it kept throwing various error codes like Exchange server error 451, Exchange server error 452, and Exchange server error 471.
Since the IS wasn’t starting and they weren’t able to gather much information about the error from the event log, the client couldn’t proceed with their regular server activities and badly needed a quick fix. Read on to find out exactly how we helped them to overcome this issue.
Finding the real cause behind IS Error 1053
Understanding why an error happens is crucial in determining its resolution. Here are some probable causes of the Information Store error 1053:
- · Incompatible .NET Framework installation against the service pack for Exchange Server
- · Inability of Exchange System Attendant in finding any of its default containers: Exchange Enterprise Servers, Exchange Services, and Exchange Domain Servers
- · Missing or corrupt jcb.dll file in callback library
- · Unexpected system shutdown
- · Incorrectly writing data to the disk
Depending upon what the exact cause for the error is, the next section contains a list of solutions you can try out to fix it.
Solutions to Exchange IS error 1053
Note: The following fixes work to solve Exchange server error 451, Exchange server error 452, and Exchange server error 471. Try the below mentioned solutions one at a time. Move to the next fix if the previous one doesn’t work.
- · Ensure that the latest updated .NET Framework is installed for Exchange
- · Ensure the Exchange Storage Group exists in one of its default containers
- · Copy jcb.dll file from Exchange 2003 SP2 installation disc to “Exchsrvr/bin” folder
· Follow the below mentioned steps:
1. Open Windows NT Event Viewer and verify the log for following services:
§ EDB file
Note: If the event log shows any other error apart from “Out of the disk” or one that suggests using “isinteg-patch” command, proceed further. Else skip to the sure-shot remedy discussed in the last section.
2. Shut down all running Exchange services and reboot the server. Restart the server to automatically restart the IS; when that happens the IS will automatically try to restore the database into consistent state.
3. Make a full online backup of Exchange IS database (including all EDB, STM, and LOG files)
4. Now initiate a full restore of the backup and ensure that the “Start Services after Restore” option isn’t enabled. When the IS starts, it replays the existing log files bringing the information store to functional state and if this step is processed successfully, you can be sure that no data will be lost.
5. Go to event log and check the log files for the EDB file. If they contain any message indicating that there was problem while replaying the log files, then open the Mdbdata folder and remove corrupt log files that. Once this is done, restart the IS.
6. If step5 doesn’t work, initiate a full online backup. Enable “Start Service after Restore” option and select “Erase all Existing data”. This will restore data to the point when backup was last taken.
7. Note: This step will involve the erasing of existing data in the IS. Hence proceed with caution. If you cannot afford any loss of data, skip to the sure-shot remedy discussed in the last section.
8. Now start “Exchange Server Administrator” program, click on “Advanced” tab and run “DS/IS Consistency Adjuster”.
9. If these steps fail to eradicate the error, then the last resort is to wipe the Information Store. To wipe out stores, backup database and delete EDB, CHK, LOG, and STM files.
Note: The process to wipe private and public IS will result in irrecoverable deletion of mailbox data and public folders. To revive the IS without any loss of data, skip to the sure-shot remedy discussed in the next section.
Sure-shot Remedy to Exchange IS error 1053
If none of the above methods work or you wish to avoid any data loss, repair Exchange EDB file using Stellar Phoenix Mailbox Exchange Recovery software. This advanced tool is undoubtedly the most sure-shot way of getting rid of problems like Exchange server error 451, Exchange server error 452, and Exchange server error 471 which stem from Information Store issues like the error 1053. Backed by powerful scanning and repair algorithms, this product helps users repair even the severest of damage and corruption in Exchange EDB files and recover the data saved within them. Find all there is to know about this product here: https://www.stellarinfo.com/edb-exchange-server-recovery.htm
If the solutions discussed above don’t work, use Stellar Phoenix Mailbox Exchange Recovery to recover the Information Store data. Once the database has been recovered, reset the IS to give things a clean start.