Know how to fix Exchange error 1053 the service did not respond to the start or control request

System Attendant service in Microsoft Exchange server is totally responsible for the superb performance of this application. The working of Information Store also depends upon Microsoft Exchange System Attendant service without which database cannot be mount and the related services stops working giving you Exchange error 1053 the service did not respond to the start or control request and related ones.

Consider a practical scenario where you are unable to start Microsoft Exchange System Attendant service following which this error message appears on screen:

“Could not start Microsoft Information Service on local computer, Error 1053: The service did not respond to the start or control request in a timely fashion”

After this error message, you also get the following description in event log after which entire data stored within Information Store becomes inaccessible:

“Event Type: Warning
Event Source: MSExchangeSA
Event Category: General
Event ID: 9157
Date:
Time:
User: N/A
Computer:
Description: Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. Wait for replication to complete and then check to make sure the computer account is a member of the "Exchange Domain Servers" security group.”

Cause:

When groups like Exchange services, Exchange domain servers, Exchange Enterprise servers are not present in Users container at the time of System Attendant service startup, Exchange server error 1053 the service did not respond to the start or control request occurs. One more reason can be edb file corruption.

Solution:

So, to fix the above encountered error, you need to immediately transfer Exchange services, Exchange domain servers, Exchange Enterprise servers like groups into Users container and then make an attempt to start Microsoft Exchange System Attendant again. But after this, even the error remains then go for Exchange server database repair to fix up the corruption issues existing there which can be performed with the help of eseutil/p command. But if it does not help, then the best solution is to go for edb repair tool that repairs up the exchange database corruption problems completely and help you to get rid of Exchange error 1053 the service did not respond to the start or control request.