Server Management - Systems Insight Manager
1836433 Members
2648 Online
110100 Solutions
New Discussion

Error on Automatic updates for VCRM

 
Steve_466
New Member

Error on Automatic updates for VCRM

Getting the following error:

Error fo file: catalog.xml
Error code: 12015
The request to connect to and log on to an FTP server failed.
Failed to open URL.
ftp://ftp.hp.com/pub/softlib/software2/COL3293/catalog.xml


Thought it may be a authentication problem but manually browsed to the software2 directory in the above URL without problems. Tried to go to the COL3293 and got doesnt exist or I dont have access. Have I missed something to make this config work. Automatic update have failed since configured all with the same error.

Any input would be helpful.
Steve
3 REPLIES 3
Rob Buxton
Honored Contributor

Re: Error on Automatic updates for VCRM

Steve,
Not sure if it's related but I've had problems accessing material on the Drivers and Software Pages. I get right through to the download button, the text seems to indicate it is 0B in size and then I get a page not found error.

I think something is broken in the whold software repository area.
I e-mailed to what seems to be the address to report errors but I've not heard anything.

Rudolf Grob
New Member

Re: Error on Automatic updates for VCRM

We encounter exactly the same symptoms with slightly different error code. somewhere I read, that hp has an Problem with this functionality. Is everyone eles working fine with VCRM downloads?

ERROR:

VCRM log entry: https://SERVERNAME:2381/vcrepository/log?entryId=VCRM1090667037
Error for file: catalog.xml
Error code: 12003
An extended error was returned from the server. 550 /pub/softlib/software2/COL3293/catalog.xml: Not a directory.

Failed to open URL.
ftp://ftp.hp.com/pub/softlib/software2/COL3293/catalog.xml

Chris Corley
Occasional Contributor

Re: Error on Automatic updates for VCRM

I realise this is an old thread now, but I am getting the same problem.

I am using SIM4.2 and am trying to get the updates through a proxy server.

Has anyone resolved this problem since these postings?

Thanks
Chris