Topic Last Modified: 2010-01-28
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 |
^(1108|1109|1110|1111|1112)$ |
Event Source |
MSExchange Autodiscover |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Client Access/Auto Discovery |
Rule Name |
An unexpected provider error occurred in the Autodiscover service. |
Explanation
These Warning events indicate that an error occurred when the Microsoft Exchange Autodiscover service was trying to load an assembly on the Microsoft Exchange Client Access server.
The following provides information about the specific causes of this alert based on the event or events that are logged in the Application log:
- Event ID 1108 This event is logged because the
Microsoft Exchange Autodiscover service found the managed
assembly or DLL it was referencing but did not load the assembly.
More information about the event is captured in the event error
description (%1), violating assembly name (%2), and in a stack
trace (%3).
- Event 1109 This event is logged when the
loader that Autodiscover is using to load an assembly or DLL has
failed because the loader could be invalid. More information about
the event is captured in a stack trace.
- Event 1110 This event is logged when the
Autodiscover provider is unable to load the assembly it is
referencing because the assembly or DLL could be in an invalid
format. The exception is thrown when the file image of a DLL or an
executable program is invalid. More information about the event is
captured in the stack trace in the event description.
- Event 1111 This event is logged when
Autodiscover is unable to load an assembly because the assembly
file does not have appropriate access permissions (executable and
read permissions). The exception is thrown when a security error is
detected. More information about the event is captured in the stack
trace in the event description.
- Event 1112 This event is logged when
Autodiscover is unable to find an assembly or DLL that it is trying
to reference. The exception is thrown when an attempt to access a
file that does not exist on disk fails. More information about the
event is captured in the stack trace in the event description.
User Action
To resolve this warning, do the following:
- Review Microsoft Exchange Autodiscover events in the
Application event log for information about the cause of this
issue.
- Contact Microsoft technical support with the stack trace
for the event. Go to the Exchange Server Solutions Center page at the
Microsoft Support Web site. From the
Exchange Server Solutions Center page, click
Assisted Support Options and use one of the assisted support
options to contact a Microsoft Support professional.
For more information about the Autodiscover service, see Managing the Autodiscover Service.
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.