Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

Resolve Error 1053 “Exchange System Attendant service could not start”

Mark Jonathan Smith | February 23rd, 2015 | general

For the Exchange Server to work in a right manner, There are a lot of Exchange services and sub-component that are required to be run properly. One of such service that should be run properly is Microsoft Exchange System Attendant. It is used to regulate the internal functions of Exchange Server. If It is not working, then services related to Exchange will not work properly and the users will report Error “Error 1053: The service did not respond to the start or control request in a timely fashion.” The database of the Exchange server becomes inaccessible when such error is reported.

exchange-recovery-new

Now to resolve the error to access the data from the Information Store (IS) perform the steps mentioned below:

1). Incompatibility of the .NET framework with the Service pack of the Exchange Server is also a probable reason for the Exchange Error 1053. Check for the update version of .NET framework.

2). The error may be reported due to the missing of jcb.dll file from the callback library. To resolve, just copy the jcb.dll file from the disc of Exchange 2003 SP2 to the folder Exchsrvr/bin.

3). Repair the EDB database using Eseutil Command

4). If you are not able to perform recovery of database using Eseutil command, then try to recover data from the updated backup

More information on the Exchange Error 1053

If the information store is corrupted due to various reasons like: Improper Shutdown, Virus Attack, etc will result into the Error 1053. The methods suggested above will help you to resolve the error. If you are not able to resolve the error using the steps mentioned above than steps mentioned below will help you to start Exchange Information Store (IS).

At  first, open the Event Viewer and verify the log for the services mentioned below:

  • MSExchnagePub
  • MSExchnageIS
  • MSExchnagePriv
  • EDB File

Two possible errors may be encountered in the Event log

1). Out of Disk

2). An Error suggesting you to use Isinteg-Patch Command

In case if any other error is reported than proceed further

#. Shut down all the Exchange services and reboot the system. The process will automatically try to restore the database into the consistent state

#. Create a complete online backup of the IS database. The backup should have all files included in it ( EDB, LOG, STM file).

#. After taking the complete backup of the IS database, restore it and ensure that you have disabled the service after the restore option. When the information store (IS) starts working, it will automatically replays the Log file and the process will automatically bring the Information store to the functional state.

#. In case if the previous step has not been executed in a proper manner,  then check the log files of EDB file from Event log. If there is a message saying that there was a problem in replaying the log files,  then delete the log files from the Mdbdata folder that are corrupted. Now restart the IS.

#. If previous step does not work for you then restore the complete online backup. Now enable the Start service and erase all the existing data. The process will automatically restore the data to the last backup point. Now Run “DS/IS Consistency Analyzer” by clicking on the advance tab from the Exchange Server Administrtator.

#. If any of the steps discussed above does not resolve your issue that you should go for third party tool to resolve the error. One such utility that I have personally used is Exchange Recovery Software that is enough to resolve the error.

Conclusion: –

In the article discussed above, I have explained the main causes and possible solution to resolve the Exchange error 1053. In case, if you are facing any difficulty while performing the recovery operation that please comment we will sort out your query as soon as possible

The following two tabs change content below.

Mark Jonathan Smith

Mark Jonathan Smith is a Tech. Blogger & he wrote posts on various topics related to Exchange Server & MS Outlook issues, conversion & migration. Mark is a MCITP certified & he continues focus on Active Directory, Exchange Server & Outlook.