Topic Last Modified: 2010-04-27

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.

Details

Product Name	Exchange
Product Version	14.0 (Exchange 2010)
Event ID	1005
Event Source	MSExchangeSA
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Mailbox/System Attendant
Rule Name	An unexpected System Attendant error occurred. Review the event description for the error that was logged.

Explanation

This Error event indicates that there are problems starting Microsoft Exchange System Attendant service. You may see this event with different error codes and different error strings. The accompanying events in the application logs may help determine the root cause of this error. Generally, this event is logged if one or more of the following conditions are true:

There are problems communicating with a domain controller or there is no working domain controller available.
The Exchange server that logged this event is not correctly registered on the DNS server.
Exchange System Attendant service is configured to start under an account other than Local System account.
The Exchange server that logged this event is not a member of Exchange Servers security group.

User Action

To resolve this error, do one or more of the following:

Use the Ping or PathPing command-line tools to test basic connectivity with the domain controller. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems at Microsoft Help and Support center.
Run the Dcdiag command line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag.
Make sure that the server the logged this event is correctly registered on the DNS server. For more information see Administering DNS Server.
Make sure that Microsoft Exchange System Attendant starts under Local System account. Follow these steps:
1. In the Services snap-in, right-click Microsoft Exchange System Attendant, and then click Properties.
2. On the Log On tab, under Log on as option, make sure that Local System account is selected.
Make sure that the Exchange server that logged this event is a member of the Exchange Servers security group.
Review other related events in the Application log and System log for Warning events and Error events. These related events may provide more information about the root cause of this error.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.