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 |
2601 |
Event Source |
MSExchange ADAccess |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Active Directory Access |
Rule Name |
Exchange couldn't get the SID for an account. The Exchange Active Directory Topology service will continue starting with limited permissions. |
Explanation
This Warning event indicates that a Lightweight Directory Access Protocol (LDAP) search performed by an Exchange component failed. In absence of other events, this event usually means that there is a problem with a specific user or operation. Mail flow should not be affected.
This warning may be caused by the following conditions:
- Domain controller configuration issues
- Network connectivity problems
- Permissions problems
User Action
If this event is rarely seen, it can safely be ignored. If this Warning event is logged at specific times or if any other pattern is detected, do the following:
- Check the Application log for related events. The detail in
other MSExchange ADAccess events and other events may help
determine the root cause of this warning. Increase diagnostic
logging for the MSExchange ADAccess\Topology category to
Lowest or higher. For detailed information about how to
increase logging, see Manage Diagnostic Logging Levels.
- 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.
For more information about the Get-EventLogLevel and Set-EventLogLevel diagnostic logging cmdlets, see the following topics:
- get-eventloglevel
- Set-EventLogLevel
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.