SCOM / OpsMgr 2007 R2 : There are no more endpoints available from the endpoint mapper

May 26, 2012 at 6:52 am in Uncategorized by Christopher Keyaert

Dear All,

Yesterday, I moved some agentless monitored servers from a Windows Server 2003 R2 SP2 management server to a Windows Server 2008 R2 SP1 management server. Since I did that, I received the following alert for all my Windows server 2003 agentless servers :

There are no more endpoints available from the endpoint mapper

Description:

The Windows Event Log Provider is still unable to open the System event log on computer ‘xxx.xxx.com’. The Provider has been unable to open the System event log for 68400 seconds. Most recent error details: There are no more endpoints available from the endpoint mapper. One or more workflows were affected by this. Workflow name: Microsoft.Windows.Server.2003.OperatingSystem.ServerServiceConfiguration Instance name: Microsoft(R) Windows(R) Server 2003, Standard Edition Instance ID: {62B32BAB-6D06-9152-EDA8-F8D4306B5D56} Management group: OM2007

In the management server event log, the following event was recorded:

The Windows Event Log Provider is still unable to open the System event log on computer ‘xxx.xxx.com’. The Provider has been unable to open the System event log for 336240 seconds.

Most recent error details: There are no more endpoints available from the endpoint mapper.
One or more workflows were affected by this. 
Workflow name: many
Instance name: many
Instance ID: many
Management group: OM2007

I checked the firewall settings, DNS settings, …. everything was fine. Finally I moved back an agentless monitored server to a Windows Server 2003 R2 SP2 management server and the error disappeared.

The Microsoft Premier Support confirmed it me, a Windows Server 2003 agentless server must be monitored by a Windows Server 2003 server watcher node. Same idea for a Windows Server 2008 agentless server, it must be monitored by a Windows Server 2008 server.

Now, an agentless watcher node could be a management server, or any other agent monitored server of you infrastructure. If you choose an agent monitored server as watcher node, don’t forget to set change the run as account of the agent to an account which has the necessary access right to the agentless monitored server.

Regards
Christopher KEYAERT
clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008