topic Re: Version Control Agent and Repository in Server Management - Systems Insight Manager

Version Control Agent and Repository

Koonan — Thu, 06 Jul 2006 11:55:38 GMT

I had to rebuild my SIM server and now I'm having problems configuring my Version Control Agent on my servers. I get the following error:

***************
No inventory information is available to obtain a list of Support Packs from. A valid Version Control Repository Manager that contains one or more Support Packs must be configured before a Reference Support Pack may be selected. If you have just selected a repository, please wait a few minutes and then refresh this page.

Previous Value: bp000264.xml
***************

I've configured the Repository and it has downloaded everything. It's been a good couple of days, and I have it downloading each night.

Re: Version Control Agent and Repository

Darrin Rawls — Thu, 06 Jul 2006 22:29:03 GMT

In the VCA, did you put in the current credentials to connect to the VCRM? Maybe these changed? the VCA needs to "log in" to the VCRM for security purposes, and without this, it will not be able to get the data.

Try this on one, once you get it working, you can use the Replicate Agent Settings task in HP SIM to push the configuration to other devices (provided the trust relationship is setup of course).

Re: Version Control Agent and Repository

Koonan — Fri, 07 Jul 2006 08:28:15 GMT

Yes I'm using credentials that have rights to this server. I've tried several different users, all had local admin rights.

Re: Version Control Agent and Repository

Rich Purvis — Fri, 07 Jul 2006 09:43:24 GMT

As an FYI do not use "Administrator" as your credential - that is one ID that is not allowed unless it is being used for backwards compatibility in an upgrade from an older working VC configuration.

-Rich

Re: Version Control Agent and Repository

Koonan — Fri, 07 Jul 2006 09:53:02 GMT

No problem, these are all "Domain" users that have local admin rights.

Re: Version Control Agent and Repository

CG_2 — Fri, 07 Jul 2006 14:03:20 GMT

This is just slightly off topic...

What rights does the ID that VCA uses to communicate with VRCM need?

Does it need to be an "administrator" on the VCRM system?

Can it be just a an otherwise unprivledged user or even guest?

I couldn't find that detail in any of the docs.

Thanks in advance.

Re: Version Control Agent and Repository

Rich Purvis — Fri, 07 Jul 2006 16:11:03 GMT

The ID only needs "administrator" or "operator" privilege in the System Management Homepage that is running VCRM - it does not have to have any level of usage whatsoever in the OS. For example:

You can create a user called VCAdmin, no special rights. You then create a group in the OS called VCAdministrators. You then place VCAdmin in the group. You tell the SMH that VCAdministrators has Administrator or Operator level rights. You then tell all your VCA's to use VCAdmin. You now have a userid for VC that has no special OS rights at all.

-Rich

Re: Version Control Agent and Repository

Koonan — Mon, 10 Jul 2006 16:29:59 GMT

The account I'm using has Administrator rights in SIM. It's the same account I'm using to run Insight Manager service. I've also tried my account that also has Admin rights on the server and in SIM.

Re: Version Control Agent and Repository

Ananthak23 — Mon, 10 Jul 2006 18:58:51 GMT

Koonan,

You might try verifying that the downloaded support packs shows up as 'valid' in the VCRM homepage and the support pack for the requesting operating system is in the Repository.
(If you are trying to configure VCA on a Windows 2000/2003 system, then make sure that support pack for Windows 2000/2003 is present and valid in the repository)
You might try rescanning the repository once the support packs have been downloaded to the repository.

Good luck,
Anantha

Re: Version Control Agent and Repository

Koonan — Tue, 11 Jul 2006 09:25:10 GMT

Go figure, leave it alone for a week, come back and it fixes itself. The Repository was fully populated when this problem started. I won't try to explain it, it works now and I'm happy. Thanks for all of the help.