VCRM will not Update from Web "AutoUpdate"

[Daniel Thrun]

Greetings. OK new at the 4.2 version of HPSIM but not new to the older ways of VCRM. The latest version I have 2.1.0.720 installed but it will not Update from HP.COM.

I read the error message when it was first installed about that the new version requires at least 1 VCAgent system to use this repository for it's VCRM, BEFORE it will allow for autoupdates. I have not only the local server, but 4 others systems pointing to the VCRM and working OK. The "Agents" servers are communicating to the VCRM and I get my status from the nodes, but still the VCRM will not update from the HP.com site. Both the VCRM and agents are using a Domain level account that have admin rights to them all, and can authenticate to the new VCRM site, and I have tried the original agents Administrator accounts also all with the same issue. NO updates.

I get this error message, when I click the update from hp.com now link within the Catalog tab.

The automatic repository update failed because an error occurred while retrieving the download site catalog.
Additional Data
Error for file: catalog.xml
Error code: 12029
The attempt to connect to the server failed.

I have opened a support case on this, but I am very unimpressed with the latest version of VCRM. The older version that I have running has NO issues with the VCAgents and or downloading. Very Ridiculous. Anyway I cannot locate any white papers on the site that I can find so if you have any let me know. AND THANKS!

[Gabriel Aguilo]

Hey there,

The VCRM service on the CMS server, needs to have a domain admin account which can access the internet via your proxy/firewall. It doesnt like using the system logon account.

Stop the service, change the logon account, then restart the service.

You will see if it works, by going to configure autoupdates again.

Ta,

Gabe

[Peter Stringer]

I have done this and strangely all my VCA agents now can connect to the VCRM which sits on the SIM server.

Previuosly they could not access the VCRM.

regards

[Daniel Thrun]

Greetings again. I read the white papers that were out there and I had also configured the VCRM services to use and authenticate using a Domain Level Account, stopped, started, restarted the service with the same result.

Severity Error
Date / Time 3/3/2005 11:09:58 PM
Message The automatic repository update failed because an error occurred while retrieving the download site catalog.
Additional Data
Error for file: catalog.xml
Error code: 12029
The attempt to connect to the server failed.

I have no issues connecting to any HP or Compaq HTTP or FTP site, or downloading from it. The VCRM just won't get auto scheduled.

Thanks though but still the agents will not get updates from hp

[Keith Rogers]

When you step through the configuration of the VCRM (using the browser), does it allow you to configure the auto-update and any proxy settings? The final step when you click "Finish" does a test download, so if the settings can be saved Ok, it *should* work when the scheduled or immediate update are run. Sorry you're having problems!

[Daniel Thrun]

Greetings. I can configure the VCRM agent all the way through with frequency etc and when I goto save it it errors out with this.

Error: unable to connect.
The attempt to connect to the server failed.

I have went into the registry and checked the settings for the ftp that the VCRM is trying to get to, and if I open a browser windows I can get to the page etc withouth issue. I noticed that in my registry and looking at my other 2 repositories that not all of the entries are there like Log File location etc.

My next step would be to install it elsewhere, see if it connects correctly and then just import that registry entry from the workin VCRM into my non working one etc., Will let you know what I find...

[Keith Rogers]

It really sounds like a proxy server configuration problem. With MS ISA/proxy set to authenticate, configuring the VCRM service to run under an accepted account *should* cure the problem.

If you logon yourself with the account used for the VCRM, does the browser test of the FTP site still work?

There is a problem with the reinstall of the VCRM which will reset its Win32 service logon account back to "system." If you've reinstalled the VCRM, check the service properties again.

If you're using a MS proxy and none of these work, then if you can supply the configuration/options that the proxy server is using, we can try to recreate the problem.

Finally, if you're using a non-MS proxy, setting the login information in the VCRM proxy settings dialog is usually the right solution (vs. changing the service logon account).

[Daniel Thrun]

To all greetings. I do thank all of your responses as they are appreciated. This is a status update from what I have done since. I have located 3 other server exactly like mine in every way (DL 380 G4, Windows 2003 etc) All Servers were on the same subnet etc. Fully Patched etc and was successful at installing and configuring and getting them to autoupdate successfully without issue. For each of these I had 1 "client" using them as it repository and it all worked even WITHOUT a domain level logon. I did not believe that for 1 second that it was proxy related as we have no proxy servers in our company that we use. Un-installing etc clearing the registry, rebooting, re-installing all had the same effect. I am right now testing out if older versions of the VCRM are successful in working. So far version 2.05 and it also would not allow autoupdates. I could save the configuration for autoupdate but still will not work! I even copied Regsitry settings from another working system for the VCRM and it did not help either

This is crazy...

any other ideas!

[Daniel Thrun]

Also I I can copy the ftp site out of the registry for the VCRM and past this into an IE Browser and it works without question....

[Keith Rogers]

I'm sorry you're having problems with one installation of the VCRM.

Older versions (with the auto-download feature, i.e., prior to 2.0.7.10) did not test the connection prior to saving the update settings, but, "in general," the auto-download process is largely unchanged from the first release of that feature. I would be very interested to know if you were able to install an earlier version of the VCRM that did successfully complete the auto-download, while a newer version did not (on the same system). Then, let me know the versions, so we can try to see what might have changed.

So, sorry, again, about the proxy-server logon "wild-goose chase," but proxy configuration, or VCA connections have been among the more typical problems.

At this point, I'm not sure what to suggest, since you have it working on 3 systems and not working on another. It seems there must be some difference (software firewall??) in the systems or their configuration, but if you can use the IE browser on that failing system to browse to the FTP catalog, it is truly puzzling.