Could not contact the VMM service

[Neal Bowman]

I have a new install of SIM5, SP5 on a DL360G5, running Server 2003, standard edition.

I also have a DL580G4 running Server 2003, Enterprise Edition, x64 version. On this server, I have installed MS Virtual Server, x64 version. I can see each of the machines that are associated with the host machine, but when I click on Virtual Machines on the Identity tab, I only get the message "Could not contact the VMM service."

When I click on the VM Performance tab, I get the following: "Communication has been lost with the VMM service.
VMM Information will become accessible once the communication with the CMS is re-established.
For more information, refer to the troubleshooting guide. "

The troubleshooting guide is useless. I have stopped and started the VMM service on both CMS and managed host server, but to no avail. I have followed advise under other threads (http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=976953) to stop the VMM service, kill the process for hpvmmsvcj.exe (this goes away when the service stops), then restarted the VMM Service.

This is the third installation of SIM5, and the VMM package has never provided any good info. Any useful information would be greatly appreciated!

I have attached a Word doc with screenshots from SIM showing the errors, versions installed, and VMM license applied to the host.

Thanks in advance.

Neal

[Rob Buxton]

You usually see that when the VMM Service has stopped.
Is that happening?
Also what version of the VMM? 2.0.2 is the latest, if you don't have that update the VMM you have.
The other thing I do that seems to make things easier is ensure WBEM is enabled for the Virtual Servers.
You'll need WBEM enabled Globally in HPSIM and you can enter global credentials if you want or leave those blank and just enter them for specific servers.

[Neal Bowman]

Rob,
The version of VMM is the version that shipped with the SIM-SP5 package. Help/About HP SIM confirms it is version 2.0.2.

The VMM service is not stopped, nor are there any entries in the event log indicating it has stopped/restarted. I have configured WBEM to use a domain account at the Global Protocol Settings page, and it is enabled.

Thanks for the insight. Any other thoughts?

Neal

[Rob Buxton · Accepted solution]

That is the latest VMM version, just a thought, you mention the x64 version of MS Virtual Server, is that supported by that version of VMM?

I'm waiting on VMM 2.1 as it will support VMWare ESX 3 (& 3.0.1). Otherwise I can't offer much else.

[Neal Bowman]

You may have hit the nail on the head. I do not see x64 listed as a supported version of MS Virtual Server, only x-86 servers.

Do you know if VMM 2.1 will support x64 MS VS?

[Rob Buxton]

Sorry no, most of the noise on this forum as been about the delay in supporting VMWare ESX 3.

[stefano colombo_1]

Hi
this is from VMM 2.0 support matrix

Microsoft Virtual Server 2005 R2
Microsoft Virtual Server 2005 R2 is supported on the following
operating systems:
â ¢ Windows Server 2003 R2, Standard Edition
â ¢ Windows Server 2003, Standard Edition Service Pack 1
â ¢ Windows Server 2003 R2, Enterprise Edition
â ¢ Windows Server 2003, Enterprise Edition Service Pack 1
â ¢ Windows Server 2003 R2, Standard x64 Edition
â ¢ Windows Server 2003, Standard x64 Edition
â ¢ Windows Server 2003 R2, Enterprise x64 Edition


So it SHOULD work but it doesn't because is such a poor product ....

Stefano