VCRM Errors

[Gerald LaVallee]

My manager has been getting updates for the last 12 months until now. Actually, since PSP 7.70 was downloaded I get the following error manually and during the automatic scheduled download:

Entry Details
Severity Error
Date / Time 7/3/2007 8:27:36 AM
Message The automatic repository update failed because an error occurred while retrieving the download site catalog.
Additional Data
Error for file: C:\hp\hpsmh\data\webapp-data\vcrepository\catalogindex.xml
Error code: 2147500037

Invalid HTTP status 502 trying to read file remote file ftp://ftp.hp.com/pub/softlib/software2/COL3293/catalogindex.xml.
Error downloading remote file ftp://ftp.hp.com/pub/softlib/software2/COL3293/catalogindex.xml to local file C:\hp\hpsmh\data\webapp-data\vcrepository\catalogindex.xml.

I have verified the account, the ISA Server and port are all valid and open. Has something changed?

Jerry

[Marco Kuenzelmann]

I am encountering the same error and the file size of ftp://ftp.hp.com/pub/softlib/software2/COL3293/catalogindex.xml is zero.
I've also checked via a direct internet connection (without any proxies) and the file is absolutely empty.

We have the newest available version of VCRM installed (2.1.8.780) and working since it was released.

[Peter Conlan]

I am getting the same error. It started for us on July 7th. We update our repository every night, and it was working fine until then.

I too manually ftp'd to the file specified and saw that it is zero bytes in size.

[Marco Kuenzelmann]

The mentioned file was regenerated yesterday, so the VCRM works again.

[Sg_6]

Entry Details
Severity Error
Date / Time 9/11/2007 9:01:25 AM
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: 2147500037

Error downloading remote file ftp://ftp.hp.com/pub/servers/software/WindowsIntegrity/catalog.xml to local file C:\hp\hpsmh\data\webapp-data\vcrepository\catalog.xml.

I got this error right now.
Perhaps some members of the pool still have the 0 byte file?

[Gerald LaVallee]

I still get the same error; I have been manually updating the repository until HP fixes or addresses this issue!

[Sg_6]

Called 1-800 HP Invent (1-800-474-6836)
They are aware of this and are working on it. No ETA.
I have a case number and have asked them to call me when it's fixed.
Considering all the different kinds of servers we have and 2 insight manager servers its not really an option to do this manually.

Perhaps if more people call someone will get on this.

[Rich Purvis]

You are all talking about different files.

Currently, as of just a few minutes ago, both of these files were accessible (and are the ones originally mentioned in this thread):

ftp://ftp.hp.com/pub/softlib/software2/COL3293/catalogindex.xml

(This is the catalog index file.)

&

ftp://ftp.hp.com/pub/softlib/software2/COL3293/catalog.xml

(This is the catalog file for Proliant PSP software)
=================================


The file that seems to be having problems currently is a 3rd file:

ftp://ftp.hp.com/pub/servers/software/WindowsIntegrity/catalog.xml

(This is the catalog file for the Integrity software downloads)

If you are using just Proliant servers then you should be getting the downloads through the currently published catalogs. Last publishing for that catalog was 8/24. The only people that should be seeing issues right now are people trying to get Integrity downloads. As stated in this thread - I beleieve they understand that there is an issue with this catalog and are trying to get it fixed.

-Rich

[Sg_6]

Yes
ftp://ftp.hp.com/pub/servers/software/WindowsIntegrity/catalog.xml
is the file that is showing in the log.

I am NOT getting any Proliant Support Pack updates.

[Marco MM]

To solve the problem the service "HP Version Control Repository" must start with cre3dentials of an user account having Administrator privilege on HP SIM box.

[Sg_6]

The account I use is an Admin
HP support knows the issue is on their end, says they will get to it eventually.
And will not call me back when it is fixed.
basically they accept my support call say they know it's an issue and close the call.
if course I am not buying HP anymore so it's just a matter of time till I don't have to deal with this anymore.