Thursday, July 28, 2011

How to Solve Exchange Server Error 1053

Performance of MS-Exchange Server totally depends on the System Attendant service. Without it Exchange related services stop working. Like, Exchange server database cannot be mount, unless and until Exchange System Attendant service is not running. Information store of Microsoft Exchange also depends on Exchange System Attendant service. Data of Information store cannot be accessed. To get rid of problem related to information store and to access data of it, you can use a backup. If backup falls short to recover, then you can go for a third party Exchange server database recovery tool.

To illustrate above issue, let us consider a scenario. When you make an attempt to start the MS-Exchange System Attendant service on a server, that is executing MS-Exchange Server 2000 or 2003, MS-Exchange System service does not start. In addition to this, you may receive the below stated error message on the screen that looks exactly same as given below:

“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”

Following event ID comes on the screen in the system log:

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9188
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.

Event Type: Warning
Event Source: MSExchangeSA
Event Category: General
Event ID: 9157
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.”
After the occurrence of above error message, data of the Information store becomes totally unapproachable.

Above erroneous situation occurs when the System Attendant service starts, it finds the below stated groups in only the container of default Users:
  • Exchange Enterprise Servers
  • Exchange Services
  • Exchange Domain Servers
If the groups are absent, the System Attendant service verifies non-existence of group. Therefore, if these groups are not present in the Users container during the beginning of System Attendant service, it fails to start.
Other reason might be the corruption of Exchange Server.

Follow the below steps to solve the above problem and to access data of Exchange Server:
1.Transfer the below mentioned groups to default Users container:
  • Exchange Enterprise Servers
  • Exchange Services
  • Exchange Domain Servers
2.Start the System Attendant service again.

If the problem still persists, then it means that Exchange Server is severely corrupted. You have to repair the corrupt or damaged Exchange Server database file with the help of an inbuilt 'eseutil/p' command. It might be possible that command does not work then you can restore the file from a latest backup. If backup is unavailable, then you have a last option of a third party Exchange Server Recovery. These third party tools are only designed to carry out the process of Exchange Recovery easily and instantly.

Stellar Phoenix Exchange Server recovery is a trustworthy tool that is used to perform Exchange data recovery. It recovers EDB files created in MS Exchange 2016, 2013, 2010, 2007, and other versions. The tool is compatible with Windows 10/ 8 / 7 / Vista / Windows Server 12 and 8.  Checkout tool -

No comments:

Post a Comment