VCA does not see repository

[Ariel_7]

Peter,
No, I have a fairly small amount of Proliants and am not managing desktops, so I am using the included MSDE.
I'll likely open a case with HP on this and will report back the results.
Ariel

[Peter Fynney]

Ariel

I meant the VCA Server, is that running SQL2000? not the VCRM Server/Desktop.

[Ariel_7]

Nope, the problemed system (the VCA)is running Oracle 9iAS...But I have another running this as well without issues.
Ariel

[Peter Fynney]

Ariel,

I tried installing the VCRM on another workstation, when I connect the Faulty VCA to this new empty Repository it logs in OK.

So I emptied the Repository on the Live VCRM, and it logged in OK.

When the Repository on the Live VCRM does an Auto Update from HP and downloads its 500MB of CP and BP files, it then fails to login.

Try it and see if you get the same results.

What is it in the Repository that is stopping the VCA from connecting?

[Ariel_7]

Hi Peter,
Sounds like you're making more progress than me. This test did not work for me, I still get the above noted messages for this procedure. I hope to call HP soon about this.
Ariel

[Bengt Sjoberg]

I have exactly the same problem. VCA works fine on 35 servers, but not on the 36th. I get the message "The Version Control Repository Manager, at seljs010, could not be accessed using the specified account and password.".
The password is right. I can even bring up the VCR using the browser on the server whcih does not connect.
I have absolutely no idea what is wrong here.
TIA
Bengt

[Peter_225]

Good to see its not just the 2 of us having the same problem, I have had an incident call in with HP for some time now, case no 1202466282, but HP have not, as yet, come up with a resolution. Looks like it is becoming more popular, will keep you posted if I ever get a resolution from HP.

Pete

[Bengt Sjoberg]

After reading through the posts here I notice a few more similarities.
1. The server with the VCA problem is upgraded from NT4 to Windows 2000
2. It is running SQL server 2000 (upgraded from SQL7)
I have at least one more machine that was upgraded from NT4 to W2K but that one works just fine.
/Bengt

[Chris A. Waters]

Hi,

I am having the same issue with a Proliant 1600R. It's a Windows 2000 Server installation, our PDC. No SQL installed.

We have three other VCA's that work fine (one is a SQL server), all are on the same subnet.

Would appreciate hearing how you solve this one.

Thanks.

[Bengt Sjoberg]

The last answer is almost a year old,and I had totally given up on this.
As you may see above I had the same problem on one server using 7.2.
I have installed SIM 4.2 and still experienced the same problem.
Yesterday I tried to upgrade to SIM 5.0. It turned out to be a new install on the Management server. On the server with the problem I did not change anything, but using the Repository Manager from 5.0 as source it now worked!
So, try an upgrade of the Repository Manager (the latest version). Something has changed!

[8i5]

Hi,

This is a very old thread but we're experiencing the same problem with the latest vca and version control repository. Some servers can connect, some cannot. Tried reinstalling the vca, upgrading the repository, replicated settings from a working server...no luck..

Anyone have this issue and resolved it?

[incognito76]

What credentials do people use to connect, I found if I used a local user account from the main HP sim server, I had more success than using a domain username and password.

[Sean Ennis]

If you see a check box with the following text "Automatically Install Minimum Dependancies(sic)", uncheck it. Later on, it may start working again with that check box checked, but I haven't tested that yet.