Get rid of Microsoft Exchange System Attendant Event ID 9188 easily

System Attendnt Service is considered as one of the most important component of MS Exchange server as you are unable to mount the server in case if it does not work fine. Working of Information Store also depends upon System Attendant. But at times you might face issues while using Exhange system attendant service followed by exchange server error 1053 and the need arises for edb repair.

Consider a practical situation where you are using Exchange server 2003 and trying to start System Attendant service but insted of you get the following error message on screen:/p>

“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, the following event id is encountered in the event log:

“Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9188
User: N/A
Microsoft Exchange System Attendant failed to read the membership of group 'cn=Exchange Domain Servers,cn=Users,dc=domain,dc=root'. Error code '80072030'. Please check whether the local computer is a member of the group. If it is not, stop all the Microsoft Exchange services, add the local computer into the group manually and restart all the services. After the above error message pops up on the screen, the data saved in the Information Store becomes inaccessible.”


Exchange server error 1053 occurs when system attendant service do not find the groups including Exchange Enterprise Servers, Exchange Services, Exchange Domain Servers in default user's container and thus are not present in user's container. This is the reason why this service do not start. Another reason for exchange event id 9188 is the edb file corruption.


To fix Could not start Microsoft Information Service on local computer issue, try to transfer the aforementioned groups to users container after which restart System Attedant service. But even after this Microsoft Exchange System Attendant failed to read the membership of group error, then you must consider to repair your corrupt exchange database files using edb repair tool which is highly capable to completely repair damaged exchange server database and then you can easily get rid of event id 9157.