VC Agent trouble after upgrading to SIM 5.0

[Bjarne Rasmussen_1]

Had an perfect working installation managing 25 proliant servers, prior to upgrading the management server.

Now it takes forever to login to HP System Management Homepage, where after a long while i get a error dialog saying "A timeout occurred..." (Se attachment). then when clicking on the "Version Control Agent" I get the same dialog, followed by the error "An error occurred while formatting the page for display" (Se attachment).

When clicking on the "log" tab I get a list of events where the latest shown is saying something about a file missing (Se attachment).

I have tried just everything solving this, even by uninstalling everything (loosing all setup in process) and reinstalling.

PLEASE can anyone give me a clue as to what to do/try next.

[Bjarne Rasmussen_1]

Realized that not all may be able to view a word doc so I will upload in gif/jpg format.
This on is "A timeout occurred..."

[Bjarne Rasmussen_1]

Realized that not all may be able to view a word doc so I will upload in gif/jpg format.

This on is "An error occurred while formatting the page for display"

[Bjarne Rasmussen_1]

Realized that not all may be able to view a word doc so I will upload in gif/jpg format.

And here is the log error:

[Rich Purvis]

The "timeout" pop-up you are seeing is letting you know that one of the applications using the System Management Homepage is not responding in a timely manner. It would appear by the other messages you are getting it is probably the VC Agent. The System Management Homepage log should have an entry with the response times of all the applications anything over 90 seconds is probably a timeout. Is your VC Agent configured to point to a VC Repository Manager? Or is there a firewall or other possible problem with the VC Agent being able to contact the system running the VCRM? Something else to check would be to be sure that the HP Insight Foundation Agent service is running. Good Luck,

-Rich

[Bjarne Rasmussen_1]

Thank's for your reply Rich, and sorry for the wait.

I have just been on again to try some things and can report the following:

1. The service HP Insight Foundation Agents runs fine, as weel as all other HP services
2. The server we are talking about here is also the server with SIM 5.0 installation as well as the latest HP System Management Home page.
3. It has the very latest Support pack tool 7.3
4. It has the very latest VC Agent
5. It has the very latest VC Repository Manager
6. The old configuration had a local account used for access to the repository
7. The timeout error only happens on this server and not on any off the others, but i still get the error with the missing xml file on all servers
8. There is no firewall issues.

Iv'e attached the log file and a screendump of the services.

I'm really at my witch ends - Should i uninstall everything and start form scratch?
-Bjarne

[Bjarne Rasmussen_1]

And the services.gif

[Harry Galanos]

Bjarne,

Ensure you have the folowing SNMP entries:

localhost - one word
simsever - hostname of your sim server.

These must be entered under the SNMP service - 'Accept SNMP'.

I had the same problem, did this and everything is now ok.

[Rich Purvis]

It looks like based on the log you posted that the timeout is coming from the VC Repository. Off the top of my head I cannot think of repository setting that would cause it to take this long to load. To verify that it is the VCRM you can go to the service control manager and stop the VCRM service. After it is stopped, go and browse to the SMH. If it comes without the popup message then it is the application causing the problem. If it is the VCRM I guess it could be a bad install or perhaps something is not properly configured for it.

-Rich

[Bjarne Rasmussen_1]

Hi again
Thank you very much for trying to help. I decided to uninstall and do it all again.

Made sure I did a proper clean up i.e. remove folders and registry entries.

So after about 5 hours I now have 25 happy servers reporting to my admin server and receiving information about updates etc.

Unfortunately I still don't know what caused it.

- Bjarne