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	9054
Event Source	MSExchangeSA
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Mailbox/System Attendant
Rule Name	Name Server Provider Interface (NSPI) Proxy listener thread could not connect to the server on transport. The Winsock subsystem returned an error.

Explanation

This Warning event indicates the Name Service Provider Interface (NSPI) Proxy listener thread could not connect to the server during transport. The Winsock subsystem returned an error.

User Action

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

Try to determine which Winsock error is being returned.
Make sure that a global catalog server is available and responding.
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.

If this Warning event continues to occur, 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.
Contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Support Web site.

For more information about global catalog servers and domain controllers, refer to Microsoft Windows documentation.

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.