Unable to install OpsMgr 2007 R2 agent on 2 Hyper-V Hosts - Service Terminating
I'm trying to install the OpsMgr 2007 R2 agent onto 2 of my Hyper-V Hosts. When I run through the process, it completes sucessfully on the console, but the servers stay in Pending Management. On both hosts during the install process I get the following errors in the system event logs: The System Center Management service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. The System Center Management service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the System Center Management service, but this action failed with the following error: An istance of the service is already running. I've managed to install it on 1 of my Hyper-V hosts without a problem. The Hyper-V hosts are part of the same domain as the OpsMgr 2007 R2 server and I am using the same action account which is a member of the local admins group on all 3 Hyper-V hosts. The Hyper-V hosts are running Windows Server 2008 R2 Datacenter SP1. Any ideas? Cheers Adam.
November 9th, 2011 3:51am
Hi Do you see any errors in the operations manager event log (one of the application and services logs in event viewer) on eithe HyperV server? Cheers GrahamNew SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
November 9th, 2011 4:02am
Graham, Yes. This: The OpsMgr Connector could not connect to RC-OPSMGR.riddlesdown.local:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination. I just checked and sure enough I can't ping the OpsMgr server from the 2 hosts I am having problems with, but I can't from the host I have managed to get working. I assumed that because the install was reported as sucessful that they could communicate - this is clearly not the case. No firewalls etc enables so I will have to look at other possibilities. Cheers Adam.
November 9th, 2011 4:10am
Hi Adam It might well be that ICMP is blocked on an intermediary device ... can you do an nslookup from each HyperV server to the RMS \ Management Server? If you are allowed to install the telnet client on one of the Hyper V servers then you could also try running a telnet check from the Hyper V server against the RMS 5723 Are there any errors in the Operations Manager event log on the RMS \ Management Servers about the Hyper V servers trying to connect? Cheers GrahamNew SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
November 9th, 2011 6:51am
Graham, I've discovered that it is a routing problem on one of the switches that the OpsMgr is connected to. I've changed it's IP and moved it to a different VLAN which has the resolved the problem, until I can fix the routing issue. Cheers Adam.
November 9th, 2011 7:03am