IBM Support

DB2 Installation on Windows fails with Error 1330

Troubleshooting


Problem

Installation failure due to an invalid digital signature

Symptom

Installation will fail with the message below indicating that a Windows cabinet (*.cab) file is corrupt.


Error 1330.A file that is required cannot be installed because the cabinet file C:\temp\db2\Windows\BASE0000.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt.

The DB2 installation log will contain:

MSI (s) (B8:68) [09:22:57:577]: Validating digital signature of file 'C:\temp\db2\Windows\BASE0000.cab'

MSI (s) (B8:68) [09:22:57:577]: Hash of signed file 'C:\temp\db2\Windows\BASE0000.cab' does not match hash authored in the installation package

MSI (s) (B8:B4) [09:22:57:577]: Note: 1: 1330 2: C:\temp\db2\Windows\BASE0000.cab 3: 0

MSI (s) (B8:B4) [09:22:57:577]: Product: IBM Data Server Client - DB2 --Error 1330.A file that is required cannot be installed because the cabinet file C:\temp\db2\Windows\BASE0000.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. Error 0 was returned by WinVerifyTrust.

The location of the DB2 installation log can be found in the Related URL Collecting Data For Installation Problems.

Cause

There are multiple causes:

  • Corrupt installation media. In this case try downloading the DB2 installation media and retry installation again.
  • If DB2 is being deployed via third party application such as Microsoft SMS or BMC Bladelogic, try the installation outside of the deployment software. If the installation succeeds without any errors there is a configuration issue with the third party deployment software.
  • If DB2 is being installed from a network share, try copying the files to the local system and run setup.exe locally.
  • Un-install Microsoft patch KB978601 (see Related URL Technote Installation of DB2 LUW fails with DJ_C0000.cab has an invalid digital signature, when "Informix data source support" option is enabled)
  • Ensure the machine where DB2 is being installed has internet access and there are no firewalls preventing the Microsoft Installer from verifying the digital signature for the cabinet file.
  • Try the workaround documented in How to Workaround Error 1330...
  • Try the workaround documented in Another Possible Workaround... The executable setreg.exe is included with the Microsoft .NET Framework SDK. See links in Related URL section.

On the sample system below we see that option #3 and #9 are set to TRUE. We want to change these values to FALSE.

C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin>setreg
Software Publishing State Key Values (0x23e00):
1) Trust the Test Root........................... FALSE
2) Use expiration date on certificates........... TRUE
3) Check the revocation list..................... TRUE
4) Offline revocation server OK (Individual)..... TRUE
5) Offline revocation server OK (Commercial)..... TRUE
6) Java offline revocation server OK (Individual) TRUE
7) Java offline revocation server OK (Commercial) TRUE
8) Invalidate version 1 signed objects........... FALSE
9) Check the revocation list on Time Stamp Signer TRUE
10) Only trust items found in the Trust DB........ FALSE


C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin>setreg.exe 3 FALSE


C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin>setreg.exe 9 FALSE


C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin>setreg
Software Publishing State Key Values (0x23e00):
1) Trust the Test Root........................... FALSE
2) Use expiration date on certificates........... TRUE
3) Check the revocation list..................... FALSE
4) Offline revocation server OK (Individual)..... TRUE
5) Offline revocation server OK (Commercial)..... TRUE
6) Java offline revocation server OK (Individual) TRUE
7) Java offline revocation server OK (Commercial) TRUE
8) Invalidate version 1 signed objects........... FALSE
9) Check the revocation list on Time Stamp Signer FALSE
10) Only trust items found in the Trust DB........ FALSE

  • Ensure the Windows Installer service (Control Panel-->Administrative Tools-->Services) has been started.
  • Ensure the following Windows registry keys are set to 0x23C00 instead of 0x63C00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing] "State"=dword:00023c00

[HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing] "State"=dword:00023c00
  • If DB2 is being installed on a machine with no internet access and when its behind the firewall, ensure that new root CA certificates are installed

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Install\/Migrate\/Upgrade - Install\/Setup - Command Line","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.8;9.7;9.5;9.1;8","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21496604

Page Feedback