Version Control Password now fails after 4.2 upgrade

[NJK-Work]

Hello,

After upgrading to version 4.2 (and the new Web interface on the SIM server), the managed servers can no longer connect to VC repository using the account and password that they have always been using. I get:

"The Version Control Repository Manager, at MYVCSERVER, could not be accessed using the specified account and password."

Assuming the VC password was changed somehow during the 4.2, how do I know what the new password is or how to I go into the VC management and change it back to the original password?

Any help is appreciated.
Thanks
Nelly

[Rob Buxton · Accepted solution]

There is a new protection mechanism now being introduced in the System Management Homepage that was introduced as part of HPSIM 4.2

The docs cover it, but what I did here.
Created a new local account (e.g. VCAAccess) with appropriate password on the HPSIM Server and grant this Server Admin rights.
Change the VCA on a Server to use this account and test.
Use the replicate Settings to change other agents.
You'll find that you cannot do this for the older agents e.g. those on NT 4 servers, but they still seem to work.

[David Claypool]

This is covered in Chapter 13 of the "Installation and User Guide" at http://www.hp.com/go/hpsim --> Information Library

[NJK-Work]

Thanks to all. I actually found a different way to fix it (but involved replicating agent settings) - but the info you provided helped and at least let me know I wasnt crazy and that this was supposed to break after the upgrade.

Nelly

[Jennifer Taylor_4]

Nelly, What was your fix? I get the same issue with a fresh install and would like to keep the domain acct as useracct if possible.

[NJK-Work]

Basically, what I did was replicated the version control username and password from the HPSIM server itself (as the source) to all the managed devices. I knew the SIM server was working, cause I could get past the point where it prompts for the user name and password to connect to the repository and got me to the point where I could select which Support Pack to use as the reference pack.

Since this username/password combination worked (even though I dont know what it is), I replicated it to all the other devices and they started working.

I think once 7.2 comes out, I will be able to configure a password of my choice and it will be set when I push the Support Pack out (at least that is my hope).

Nelly