Hi,

We have been receiving the below 3 alerts related to Universal Connector. When ever we receive these alerts, forwarding of alerts from SCOM to BEM becomes very slow and takes hell lot of time. Normally the alerts would be forwarded in less than 1 or 2 minutes. But, during these alerts, taking 30-60 minutes.

The Connector service threw a WSMan COM exception when attempting to send alerts to provider

The Connector service threw an exception because no providers could be contacted to send alerts

The Connector service threw an exception because no providers could be contacted to get update events.

What could be the reason and what needs to be checked/done to overcome these alerts?

Regards,

Naren.

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Naren,

The connector is losing connection to the agent. It has a built-in retry so eventually when the connector does reconnect successfully with the agent the alerts are getting forwarded. This would explain the 30-60 minute alert time.

My guess is there are network issues that is causing the connector to lose connection to the agent. Look at the logs on both the connector and agent to see if they provide any details. See this link on how to enable TRACE logging for the connector --> http://technet.microsoft.com/en-us/library/ee809020.aspx

When this happens try pinging the agent from the Connector and see if it is successful.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, November 20, 2012 12:59 PM

Hi Steve,

The issue was resolved after we restarted the Interop Provider on BEM side. Yes, as you had mentioned there was some network glitch. Thanks for the details.

Regards,

Naren.