VCA does not see repository

[Ariel_7]

Hello,

I have the VCRM/VCA relationship setup properly on several servers. The VCAs can see the Repository and all is good accept for one server. When I go into the the VCA on the problemed server, I see the following:

The repository specified, X , did not return a result

I've verified SNMP on the bad server, looks good. I know I am using the correct password. I've just updated both the VCA and the VCRM, ran the Device ID and Software Version Status Polling...no luck. Before I updated the VCA I did an uninstall\reinstall.

Any ideas?

Thanks,
Ariel

P.S. This thread has been moved from ITRC server mgmt (Insight Manager 7) Forum to ITRC HP Systems Insight Manager Forum - HP Forums Moderator

[Jeff Mathews]

Areil, whenever I've had a problem that just doesn't seem to work from one server, like you have here, I setup a control task to replicate settings from a good server. That way you can mirror the settings from a good server to the problem server and you will *know* that the settings are identical. It seems to work for me, so I would give it a try and see what happens.

Jeff

[Jeff Mathews]

One more thing to check before doing that. On the server that is having the problems how are you excepting SNMP traffic? If you have a specified a server to accept traffic from, you must also include the loopback address as the first entry in the list (127.0.0.1)

Jeff

[Rob Buxton]

You can push the Repository details from a known good server to the bad one using a Group Configuration task.

I take it you can log into the VCA and it's when you try and configure it that you get the error.

[Ariel_7]

Jeff,

Thanks for the suggestion of setting up a control task. I'm fairly new to IM, so I haven't tried this...I'll give it a go.

I am specifying which SNMP traffic to accept, I do have the loopback as the first address and my IM7sp2 server that has VCRM as the second on that list.

Thanks.
Ariel

[Ariel_7]

Rob,

I'll check out a Group Configuration task as well.

Yes, I can launch the VCA, and when I try to authenticate to specify the Repository, I get the error. In the previous VCA version, this was all in one screen, but I still got the same error.

Thanks for the Group Config suggestion.

Ariel

[Ariel_7]

Thanks, again, but no dice. Oh well, I'll keep digging.

Ariel

[Jeff Mathews]

Ariel, have you tried pinging the repository server from your problem server? Just wondering if it can do an acurate name resolution. Maybe there is a DNS issue?

Jeff

[Ariel_7]

Jeff,

Thanks for the persistant attempts at getting to the root of my issue.

I assume I followed your first suggestion correctly as the procedure seemed fairly straight foward.

To answer your question, yes, I can ping the VCRM from the VCA in a terminal server session. However, I realised I did not paint the entire picture as I browse back through the thread...Here's additional (pertinent) info (I know...duh, sorry!)

The first msg I sent is what I see in the VCA LOG:
The repository specified, X , did not return a result

When I first go into the VCA (v2.0), I select Change Agent Settings, It then allows me to update my user\pwd and VCRM repository, I select Next, it then attempts to connect to the repository but comes back with this msg:
The Version Control Repository Manager, at X, could not be accessed using the specified account and password.

However, I KNOW I am using the right password (I am using the default Administrator account). I can say this because I've confirmed with another VCA server.
I've also re-entered the pwd several times no caps lock).

I'm stuck.

Thanks,
Ariel

[Jeff Mathews]

The server you are having trouble with doesn't have any special characters in its name does it? I've seen this kind of thing happen when it has an underscore or something like that.

[Jeff Mathews]

This one really sounds like a stumper, but I don't want to give up. Have you tried one of the other accounts like user or operator with the same password to see if it lets you press "Next" and set the reference support pack?

Jeff

[Rob Buxton]

Interesting, from what you've posted you have another Server that can talk to the VCRM okay?

You've tried using a Group Configuration Task using this Server as a template to push to the rogue Server and the login still fails? That should rule out login details providing the task completed okay.

Try browsing to https://server:2381/vcrepository and then looking at the Log File. Login Failures to the VCRM are recorded there, providing it is reaching the VCRM.

[Ariel_7]

Jeff,Rob,

No funny names on either the VCRM or the VCA, both are very simple, no dashes, no underscores.

I have tried the operator account. My understanding is that if you do not set the other "canned" accounts, they default to the password assigned to the Administrator account. So, no luck there either.

The log on the VCRM shows nothing of interest, just the "VCRM started" and "Support pack added".

Ariel

[Andrei Khairetdinov]

Hello,

I had exactly the same behaviour of the VCA, but that happen when I tried to connect to VCRM through firewall. To fix the problem I had to open port 2301 from VCA to VCRM.
What happen if you telnet from VCA server to VCRM server on port 2301 ?

[Jadrice Toussaint]

Hello -

I know you've already uninstall and reinstall the vca agent, but I have an extra step for you to take to see if that resolves your issue.

1. uninstall the vca agent
2. Remove the directory C:\compaq\vcagent.
3. reboot then reinstall the vca agent.


Test your settings now and see if you can get vca to recognize the VCRM server.

Let me know how you make out.

[Ariel_7]

Andrei,
Thanks, but the VCRM and the VCA are on the same subnet, nothing in the middle of them.
Jadrice,
Thanks for this suggestion. Because this requires a reboot, I'll be able to try this my next maintanance window. I'll let you know how this goes.
Thanks!

[Rob Buxton]

If there are no login failures in the VCRM Log, it seems to indicate that it's not getting as far as the VCRM.
That would seem to indicate some kind of name resolution issue.
Well, that's my guess!

[Peter Fynney]

I am getting exactly the same problem, it all works ok on 22 VCA's but just from one VCA I get the exact same message, I've removed and reinstalled the management agents and VCA several times, but get exactly the same error, it is on the same network segment, i can ping the VCM OK.
If anyone can come up with a solution for this I would be so grateful

[Peter Fynney]

This one Server is a Proliant 380, has Windows 2000 installed with SP4, the only difference with this server to all the rest is that it had an upgrade from Windows NT4 to 2000 Server, where as all the the others are either NT4 or 2000 fresh installs, dont know if this was the same as the server that Ariel is having problems with? Have tried ALL of the above, and is still the same, if I come across the solution, I will let you all know.

[Ariel_7]

Peter,
Thanks for sharing your problem. Did you try Jadrice's suggestion above:
1. uninstall the vca agent
2. Remove the directory C:\compaq\vcagent.
3. reboot then reinstall the vca agent.
That was my next step, but if you've gone through the pain, I'll pass.
I am on a freshly installed W2Ksp3 380G3 with VCA 2.0. I am using the the VCRM from 6.4. I'll chime in here if I come up with anything.
Ariel

[Peter Fynney]

Ariel
1. uninstall the vca agent
Yes, I Uninstalled

2. Remove the directory C:\compaq\vcagent
Yes, Removed this folder

3. reboot then reinstall the vca agent.
Yes, Version 2.0

That was my next step, but if you've gone through the pain, I'll pass.
Dont Bother, it doesen't work.

I am on a freshly installed W2Ksp3 380G3 with VCA 2.0. I am using the the VCRM from 6.4.
Oh No, Thats that one out the Window.

I'll chime in here if I come up with anything.
Thanks, Keep in Touch

Pete

[Rob Buxton]

From the Server that is having difficulty accessing the VCRM can you ping the server using the name being specified in the VCA Configuration.
Maybe even do a Traceroute (tracert.exe), again using the name, to check that it's getting to the correct Server.

Try the Login Request from the Server. Use IM to access the VCRM and check for any entries in the log, it should report a Login Failure if the credentials are invalid.

[Ariel_7]

I can ping the name of the VCRM server. Tracert reveals 1 hop (not traversing multiple subnets)
And from another posting above. >
The first msg I sent is what I see in the VCA LOG:
The repository specified, X , did not return a result
When I first go into the VCA (v2.0), I select Change Agent Settings, It then allows me to update my user\pwd and VCRM repository, I select Next, it then attempts to connect to the repository but comes back with this msg:
The Version Control Repository Manager, at X, could not be accessed using the specified account and password.
However, I KNOW I am using the right password (I am using the default Administrator account). I can say this because I've confirmed with another VCA server.
I've also re-entered the pwd several times no caps lock). <
The VCRM and the VCA logs do not show any failed login attempts. Rob mentions above, and I agree, that it does not seem to be getting to the VCRM server. The big question is why this one server can't, but others can?? Thanks for your suggestions.
-Ariel

[Peter Fynney]

I get exactly the same symtoms on ONE Proliant Server ONLY.
There are no LOG Messages in the repository Manager log about any failed login.

The VCA attempts to connect to the repository but comes back with this msg:
The Version Control Repository Manager, at X, could not be accessed using the specified account and password.

Again I know I am using the correct User/Password combination, because it works OK on 22 other Proliant Servers.

This Server is running SQL 2000, no other server is! Is this the same as your server Ariel?

[Jadrice Toussaint]

Guys -

I would recommend you open up a case with HP on this one. I considered all sorts of possibilities but came up blank.