Microsoft Exchange databases and transaction are managed by MS Exchange information store to provide information about other services and different clients those accesses mailbox database and public folder database files.
When Exchange users try to start MS Exchange System Attendant Service which is running Exchange server 2003 or 2000, the Attendant service doesn't respond. Consequently user will receive Microsoft Exchange server error 1053. In this article, we will discuss about the reasons behind the error and its solution.
Exchange enterprise server and Exchange domain server are the groups that are generated by the process in the user container at the time of server installation. These groups are also called domain local group i.e. Exchange enterprise server and global group i.e. Exchange domain server.
If both the groups are not present in the default User Container, the system service identifies that the groups does not exists. Eventually System Attendant service doesn't respond, if these groups are not founded in the User container.
To solve this most frequently occurring error, user has to follow the steps given below:
After following these steps user won't be face any Exchange server error further.
Moreover by following these steps user can face many corruption errors including Microsoft Exchange server error 1053 that effectively harm Exchange server performance. These errors affects the database of the server i.e. EDB files like mailbox database.edb, pub.edb, priv.edb or public folder database.edb etc and file becomes corrupted. In this case Exchange EDB recovery software helps user to restore EDB files very conveniently and make them healthy to be converted into Outlook PST file.