topic Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository in Server Management - Systems Insight Manager

After Update to 5.0, Version Control Agents Unable to Connect to the Repository

Roy Love — Fri, 26 Aug 2005 17:52:15 GMT

After upgrading to 5.0, all my version control agents are not able to connect to the Repository?

What did I miss?

Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository

siju_1 — Mon, 29 Aug 2005 02:32:30 GMT

Could you please give some details like
which version of VCRM you had earlier(before upgrading) and which account you were using to connect to VCRM from VCA.

Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository

Stavros Tsirakidis — Mon, 29 Aug 2005 03:22:31 GMT

Hi,

I have the same problem after the upgrade to SIM 5.0 from SIM 4.2 SP2, plus:

- System Management Homepage timeouts ( as described from Mikael RÃ¶nnbÃ¤ck in the previous thread)

- HPSIM 5.0 Cluster monitor shows blank frame ( as described from Ole Thomsen in one of the previous threads, too)

I have already opened a call for the issue with the cluster monitor. I will let you know, as soon as I have a solution therefore.

Stavros

Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository

Roy Love — Mon, 29 Aug 2005 03:41:35 GMT

Thanks, I am not going insane. Please do let all of us know the fix for this issue!

Roy

Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository

David Claypool — Mon, 29 Aug 2005 14:39:05 GMT

HP SIM installs Systems Management Homepage 2.0 as part of its process. SMH 2.0 began with PSP 7.2 and moved from using the SMH built-in accounts administrator, operator and user with passwords managed within the SMH in favor of an OS model. If your VCA was configured to access VCRM using administrator and an embedded password, after the upgrade it will need to be a valid account as in domain\administrator with the password validated against the OS/domain.

Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository

Hochmuth_1 — Tue, 30 Aug 2005 03:18:15 GMT

Some Tips:

-Check Trustrelationships + options
-Maybe renew certificates
-Upgrade to the newest VCagent (2.1.1.720)
-delete (first one for test) server from database and discover again (that helped in my case)

Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository

Jim Holley_1 — Wed, 31 Aug 2005 23:11:21 GMT

I am having this exact same problem. I have been round and round, installing/removing/re-installing the systems mgmt homepage. No matter what I do, when I go up to version 2.1.0.121 the version control agent claims that the repository is invalid. When I go back to version 2.0.2.106 everything works fine. I am using Windows domain credentials and using Administrator/Domain Admin accounts. This was all prompted by an upgrade to SIM v5 although I am no longer even involving SIM - it's been removed. I'm down to Systems mgmt homepage, version control repository and agent only. It just won't work. I must be missing the same thing. Help!?

Re: After Update to 5.0, Version Control Agents Unable to Connect to the Repository

Stavros Tsirakidis — Thu, 01 Sep 2005 05:45:27 GMT

The following steps have worked for me:

- deinstall from "add/remove programs" the system homepage, insight agents, vc agent und vc repository. Finally reboot the server

- install the components system homepage, insight agents, and vc agent from psp 7.30

- install Version Control Repository Manager 2.1.1.730 and make an initial repository ....

After all these, I tried an update to VCRM 2.1.1.740 and it DIDN'T work. I will keep the 2.1.1.730 version. The HP System Management Homepage for Windows Version is 2.0.2.106. I ain't gonna change it, too. Hope it helps!

cheers,
Stavros