Server Management - Systems Insight Manager
1753515 Members
5171 Online
108795 Solutions
New Discussion юеВ

Re: Communication with lost with VMM service message on VMM 2.0.1

 
Nancy Kafer
Frequent Advisor

Re: Communication with lost with VMM service message on VMM 2.0.1

The mxagentconfig command worked successfully. Just to make sure I used the mxagentconfig -r command to remove the server and then reconfigured it....everything processed successfully.

But when I run deploy the agent the vmcli command is still failing with the message:

Agent registration failed
Agent cannot be connected.
Nancy Kafer
Frequent Advisor

Re: Communication with lost with VMM service message on VMM 2.0.1

Ok I've figured out what was causing my issue with the vmcli registeragent command but I'm still getting the same error message:

Communication has been lost with the VMM service.
Todd Schelin
Valued Contributor

Re: Communication with lost with VMM service message on VMM 2.0.1

I have found a resolution to this sporadic issue where you lose communication with the VMM service. I was working in VMM fine yesterday and this morning go to use it and go the VMM Lost Communication with Server.

I had made no changes to anything.

My resolution:
1.Go to the SIM Server and Stopped the VMM Service.

2. Go task manager and find and stop all of the following processes.
hpvmmsvcj.exe

3. Restart the VMM Agent on the SIM server and you should be good to go.

I have been working this issue off and on for a while now and this seems to be the only thing that works.

Whether the Server is VMWare or Microsft Virutal Server the same scenario applies above.

Scott_278
Valued Contributor

Re: Communication with lost with VMM service message on VMM 2.0.1

I had the same issues, and simply restarting the VMM service on the CMS worked for me.

Re: Communication with lost with VMM service message on VMM 2.0.1

It's old thread, but I still have the same problem! Restarting VMM Service on a SIM server doesn't work for me.

I'm running:

Operating system: Windows 2003
Version: Systems Insight Manager 5.0 with SP4 - Windows
Build version: C.05.00.01.01
Build date: 2006-02-01 12:06

Plug-in applications:

HP Storage Essentials 5.0.1
HP Virtual Machine Management Pack 2.0.2
HP BladeSystem Integrated Manager 2.0.2
HP Server Migration Pack 2.0.2

Occationally, VMM works from 2 to 10 days, and then it just stops working. However, I've managed to get it working again (for 2-10 days) by reinstalling the VVM client agent to the ESX servers. But this is unacceptable.

Anyone?