Oracle Key Manager - Verified Software File Failed. Error: Software Upgrade Fail

Asset ID:	1-72-1684010.1
Update Date:	2014-09-12
Keywords:

Solution Type Problem Resolution Sure

Solution 1684010.1 : Oracle Key Manager - Verified Software File Failed. Error: Software Upgrade Fail - 'Invalid signature' error in event log

Applies to:

Oracle Key Manager - Version 2.2 and later
Information in this document applies to any platform.
When upgrading to 2.5.2, the upgrade failed indicating that the Software upload verification failed preventing the software upgrade from proceeding. The error is displayed in a pop-up window.

Symptoms

Upgrade failed from version 2.2 going to version 2.5.2 with window popup text shown below:

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

Verify Software upload file failed

Error: software upgrade failed

The dump indicates an 'Invalid Signature' error similar to below:

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

1EA8FF6916CCF65500000000003F039E 1EA8FF6916CCF655 MITC-KMA1 Local Management Operations Medium Term Retention Verify Software Upload Error Error 000156000001 2014-06-17 13:20:08.841768+00 SU1 10.xxx.x.xxx No recommended action

1EA8FF6916CCF65500000000003F039D 1EA8FF6916CCF655 MITC-KMA1 Security Violation Medium Term Retention Verify Software Upload Invalid signature Error 000156000213 2014-06-17 13:20:08.139807+00 SU1 10.xxx.x.xxx Contact Technical Support and gather a system dump if able

Cause

A signature file may need to be uploaded as part of the upgrade.

It is also possible that the patch download did not complete successfully due to browser or network issues.
When unpacked, p11874982_220_Generic.zip should include the 4 files below:
      Name                                                                                   Size      Packed Size Modified
      Build383-SUNWkms2-Build842.7-i386.tar.bz2.sign     2,040,296,557   2,039,764,051   2011-03-15 11:57
      KMS_2.2.2_Release_Document.pdf                                  250,780             240,391 2011-03-15 11:54
      license.txt                                                                    174,866            43,700 2011-03-15 11:54
      readme.txt                                                                         674                  384 2011-03-15 11:54

Solution

unzip the p1685022_250_generic.zip file and then browse to the .sign file and upload the .sign file upgrade file. Then proceed with the upgrade again.

Attachments

This solution has no attachment