topic Re: Software Version Status unkonwn - VC Agent not configured in Server Management - Systems Insight Manager

Software Version Status unkonwn - VC Agent not configured

M. Hofstetter — Wed, 19 Dec 2007 12:45:13 GMT

Hi all

Over 90% of my 500 Servers will not shown correctly in HP SIM 5.1 SP1 (with latest Hotfixes).

The Software Status will displayed as "Software Version Status unknown - VC Agent not configured".

When i click to the icon, HP SIM opens the Software-Version-Webpage without Problem.

In some rare cases it helps to delete the system and add it again.

Any ideas to solve the problem?

Tx a lot,
Mike

Re: Software Version Status unkonwn - VC Agent not configured

Jonathan Preston — Wed, 19 Dec 2007 15:32:23 GMT

I'm having the exact same problem.

The erroneous display comes up on both machines that the local VC Agent is reporting as inline (green check) with the reference support pack as well as machines that the local VC Agent reports as out of sync with the reference support pack.

In both cases my software status icon is a question mark and displays the message "Software Version Status unknown - VC Agent not configured".

I am also running HP SIM 5.1 SP1.

Re: Software Version Status unkonwn - VC Agent not configured

Rancher — Wed, 19 Dec 2007 16:34:37 GMT

I also have this happen sometimes to some of my servers. I run a Software Poll on the afffected servers and this usually takes care of it. In rare instances I have to restart the VCA service first.

Re: Software Version Status unkonwn - VC Agent not configured

CCyre — Wed, 19 Dec 2007 17:12:38 GMT

Add me to the list. :)

Re: Software Version Status unkonwn - VC Agent not configured

M. Hofstetter — Tue, 08 Jan 2008 17:32:48 GMT

Any news or someone has the problem solved?

Re: Software Version Status unkonwn - VC Agent not configured

Thomas Dupont — Thu, 14 Aug 2008 18:26:01 GMT

Add me to the list. We are experiencing the same issue.

Re: Software Version Status unkonwn - VC Agent not configured

Nick Cozby — Mon, 25 Aug 2008 20:29:28 GMT

Re-importing the security certificate on the problem server corrected this for me.