Agentless monitoring: SCOM reports "no more endpoints"
Dear Sir or Madam - I am testing agentless monitoring of Windows servers using the Microsoft-supplied MP for Windows. Most of the monitors and rules appear to be working. However, SCOM generates an alert saying - The Windows Event Log Provider is still unable to open the System event log on computer '<fqdn-of-target>'. The Provider has been unable to open the System event log for 155520 seconds. Most recent error details: There are no more endpoints available from the endpoint mapper. However, I can login to the RMS with the Management Server action account and use event viewer to access the event log of the target computer with no problem. I can also run a simple WMI script to access the event log of the target computer. Neither of these should work if there are really no endpoints available. What other problem might generate these symptoms ? Thank you. James Troy
April 20th, 2011 2:47pm

No more endpoints tells us this may be a client OS that is doing the monitoring? Yes? Client OS is limited to 10 open connections on the network. I suspect this is your problem.Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2011 7:58pm

Hello Dan - No, its not a client OS. The RMS is running on Win 2008 Standard edition. Thank you. James Troy
April 25th, 2011 8:54am

I believe server standard edition also has a connection cap.Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
April 25th, 2011 5:29pm

Perhaps there is a firewall that block something? If you use a lot of these endpoints they might use higher and higher ports. So from 1024 going up. Otherwise you might end up searching on the net for Troubleshoot RPC endpoint mapper issues or something like that.Bob Cornelissen - BICTT (My BICTT Blog)
April 26th, 2011 2:28am

Hello Bob - There are no host-based nor network firewalls involved. Thank you for the suggestions. James Troy
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2011 11:49am

Hello Dan - The RMS is running on Win 2008 Standard edition. Currently it is monitoring itself, two Windows servers with agents, and one Windows server that is agentless. At this moment "netstat" shows that it has 16 active TCP sessions in total (for all purposes, not just RPC). The agentless server is running on Win 2003 Standard edition. At this moment "netstat" shows that it has 10 active TCP sessions in total (for all purposes, not just RPC). Of those, two sessions come from the RMS to the endpoint mapper. Two more sessions come from the RMS to the Svchost process that is handling the "netsvcs" group of services. Finally, the RMS has one session to the Lanmanserver service. It seems hard to believe that this environment is pushing the limits of Windows network connectivity on either server. Its my impression that agentless monitoring is not used very much, and that is probably why none of the 365 people who have read this post have been able to suggest a resolution. If we decide to use SCOM in our environment, and if we want to make use of agentless monitoring, we'll open a case with Microsoft technical support to get a resolution to this issue. Thanks to all who have taken the time to read this. James Troy
April 28th, 2011 12:25pm

Well at least you did do the check for firewalls (in between and local), you checked rights, you checked the amount of sessions on the box and I also dont think that a server box is full that fast. And you are right, I almost never use agentless monitoring (for windows machines). It just gives much les monitoring possibilities than the agent version and I have never come across a machine that had a problem with running an agent on it. So if and i say if the endpoint mapper error is just a cover-up for a situation underneath I would troubleshoot rights as the first thing. Check for failure audits in the eventlogs on both sides. Of course you can always open a css case for this issue (if you see a chance please post the solution back here).Bob Cornelissen - BICTT (My BICTT Blog)
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2011 12:43pm

Hi James, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,Yog Li -- Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
May 6th, 2011 6:08am

Hi All, I've got exactly the same problem. I move 14 agentless from a Windows Server 2003 R2 SP2 Ent Management Server to a Windows Server 2008 R2 Ent Management Server and in the MS event viewer, I have : There are no more endpoints available from the endpoint mapper for all the agentless servers :s I moved all the agentless to another WIN2008R2 MS and exactly same error. Firewall service is running but set to OFF. Thank you Regards Christopher Christopher Keyaert - MVP - My SCUG.be blog : http://scug.be/blogs/christopher
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2012 5:29am

The solution to the problem : http://scug.be/blogs/christopher/archive/2012/05/26/scom-opsmgr-2007-r2-there-are-no-more-endpoints-available-from-the-endpoint-mapper.aspxChristopher Keyaert - MVP - My SCUG.be blog : http://scug.be/blogs/christopher
May 26th, 2012 3:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics