Issues around importing a corrupt file into HPSA

  • KM02769229
  • 05-Apr-2017
  • 17-May-2021


Sometimes the patch databases emitted by Microsoft are corrupted, which can cause problems for HPSA.


Older versions of Server Automation (SA) will silently accept corrupted copies of the patch database.  This database will then be distributed to any managed Windows server during its next software inventory.  A corrupted on a managed Windows server will cause this software inventory to always fail.  It will also cause all Windows patch remediation activities to fail.


Sometimes corrupted copies of will be present on some nodes of Microsoft's web server cloud.  Whether or not you end up downloading one of these corrupted copies will then depend on how your server resolves the hostname "".


Defensive logic was added via the following hotfix rollup line item that causes HPSA to reject corrupted files:

  QCCR1D233320 - SA silently accepts corrupted files   (note: the QCCR ID will vary from SA version to SA version)

The best workaround is to install a hotfix rollup that contains the above fix.

You can check to see if your currently installed hotfix rollup contains this fix by executing the following command on one of your HPSA slices and looking for results that match the description above.

find /opt/opsware/hotfix/ -iname readme.txt | xargs grep

Whether or not you have this fix in place, it is a good idea to manually download the to your workstation, so that you can verify that it is valid before uploading it into HPSA manually via the java client.

Once you download the cab file, you can manually verify the embedded signature by performing the following steps:

  1. right-click the cab file
  2. select "Properties"
  3. select "Digital Signatures" tab
  4. select one of the listed signatures.
  5. click the [Details] button
  6. The result of will be displayed at the top.

check signature of file