VCRM repository not updating

[Denver Miranda]

Getting messages in Version Control Repository Manager that several files cannot download because they don't exist.  If I go to the HP FTP site and drill down manually to the location to try to manually download and dump into the repository, sure enough, they don't exist.  I tried googing everywhere for these files but don't seem to find themand they seem like they are for Itanium servers.

Is there a way to suppress these download attempts so we don't get alerts for non-existent files on the FTP site?

Thanks in advance.

----------------------------------------------------------------------------------------------------------------------------------------------

Message The automatic repository update process encountered an error while obtaining one or more files from the download site. Additional Data Error for file: isp-6.20.w2k8.exe
  Error code: 12003
  An extended error was returned from the server.550 /pub/softlib2/software1/supportpack-windows-integrity/p1032086800/v49374/isp-6.20.w2k8.exe: No such file or directory.

Error for file: cp009634.exe
  Error code: 12003
  An extended error was returned from the server.550 /pub/softlib2/software1/sc-windows-integrity/p1619460899/v49239/cp009634.exe: No such file or directory.

Error for file: cp010231.exe
  Error code: 12003
  An extended error was returned from the server.550 /pub/softlib2/software1/sc-windows/p609741821/v51058/cp010231.exe: No such file or directory.

Error for file: cp010321.exe
  Error code: 12003
  An extended error was returned from the server.550 /pub/softlib2/software1/sc-windows/p1286870943/v51381/cp010321.exe: No such file or directory.

Error for file: bp000531.xml
  Error code: 12003
  An extended error was returned from the server.550 /pub/softlib2/software1/supportpack-windows-integrity/p1032086800/v49374/bp000531.xml: No such file or directory.

[shocko]

Sounds like the catalogue file (the .xml file) is listing files that do not exist on the HP backend. This can happen when updates are pulled from distribution because they were superseded or had a problem and the catalogue was never updated. Perhaps log a call with HP support and get confirmation?