Topic Last Modified: 2010-04-28
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager runs Exchange Management Shell cmdlets to monitor your Exchange organization. Running cmdlets triggers one or more Operations Manager alerts if a problem is detected.
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 events that have
been logged that meet the criteria of this Operations Manager
alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
^(2001|1001|3001)$ |
Event Source |
MSExchange Monitoring OutlookConnectivity Enterprise End To End |
Server Role |
Ex14. Client Access |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Client Access/Outlook/Outlook Connectivity |
Rule Name |
TCP Connectivity with Autodiscover - Address Book failure (NSPI) |
Explanation
The cmdlet that triggers this event is the Test-OutlookConnectivity cmdlet. The Test-OutlookConnectivity cmdlet is used to test end-to-end Microsoft Outlook client connectivity in the Microsoft Exchange Server 2010 organization. This includes testing for Outlook Anywhere (RPC/HTTP) and TCP-based connections. R0lGODlhAQABAPMAAAAAAP///////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAACH5BAEAAAIALAAAAAABAAEAAAQCUEQAO0== This Error event indicates that Test-OutlookConnectivity cmdlet could not perform a TCP Connectivity test of the Autodiscover service due to a Address Book Name Service Provider Interface error.
User Action
To resolve this error, do one or more of the following:
- Review the Application log and System log on your Exchange 2010
servers for related events. For example, events that occur
immediately before and after this event may provide more
information about the root cause of this error.
- To review detailed information about the cause of this alert,
use the Operations Console in Operations Manager. For more
information, see the introduction to this topic.
- 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.