Topic Last Modified: 2010-02-15
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 |
2389 |
Event Source |
MSExchange ADAccess |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access |
Rule Name |
A search request that was sent to the server running Active Directory didn't provide a result within a reasonable time period. |
Explanation
This Warning event indicates that a search request that was sent to the server that is running Active Directory did not provide a result within a reasonable time period. The search request was abandoned. This event is logged when the search request to the directory service did not return in less than 120 seconds.
The most frequent cause of this warning is because the domain controller is under heavy stress. This warning may also be caused if a network error is introduced at the packet level. This causes the domain controller to continuously try to resend the requested information to Microsoft Exchange.
User Action
If this event is seen rarely, it can be ignored. If this Warning event is logged at specific times or if any other pattern is detected, do the following:
- Investigate what is occurring on the specific domain controller
named in the Description section of the event and check to see
whether it is being heavily loaded.
- Use the
Ping
orPathPing
command-line tools to test basic connectivity. UsePing
to isolate network hardware problems and incompatible configurations. UsePathPing
to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.
- Run the
Dcdiag
command-line tool to test domain controller health. To do this, rundcdiag /s:<Domain Controller Name>
at a command prompt on the Exchange server. Use the output ofDcdiag
to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Windows Server TechCenter.