Topic Last Modified: 2010-02-05

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:

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

1053

Event Source

MSExchange Extensibility

Alert Type

Warning

Rule Path

Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Agents/Common

Rule Name

A transport rules agent failed to create an agent instance.

Explanation

This Error event indicates that the agent specified in the event description could not initialize because of an Exchange-specific exception. The event description indicates the exception that caused the problem.

This error may be logged if the resources that the agent requires are not available. For example, if the agent cannot connect to Active Directory, this error may be logged. It may also be logged for other reasons when attempts to create an agent instance fail.

User Action

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

  • Review the exception that is specified in the event description to better understand the cause of the problem.

  • If you suspect an Active Directory resource issue: 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 Overview at the Windows Server TechCenter.

  • Troubleshoot network connectivity issues. Use the Ping or PathPing command-line tools to test basic connectivity. 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.

  • Contact the third-party vendor who supports the respective transport agent if the transport agent is not created by Microsoft

If this event still occurs after you try to resolve this issue, do one or more of the following:

  • Disable the agent that is specified in the event description. However, if you disable the agent, you disable the functionality that is provided by the agent. For information about how to disable a transport agent, see Disable-TransportAgent.

  • Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and others. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Technical Support, be sure to review your organization's guidelines first.

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.