Use the following table to find information to help you troubleshoot some of the more common problems that you may encounter when verifying digital signatures on objects.
| Problem | Possible solution |
|---|---|
| Restore process fails for objects without signatures. | If the lack of a signature is not a concern, check to see if the QVFYOBJRST system value is set to 5. A value of 5 specifies that unsigned objects cannot be restored. Change the value to 3 and try the restore again. |
| Restore process fails for objects with signatures. | This may happen if the *SIGNATUREVERIFICATION certificate store was transferred to the system and DCM was not used to change the password for it. In such a case, the certificates that the store contains cannot be used to verify the signatures on objects during the restore process. Use DCM to change the password for the certificate store. If you do not know the password, you will need to delete the certificate store; recreate it and use DCM to change the password. |
| When restoring or installing a product, you get an error because a signature failed to verify. | When an object signature fails to verify correctly, the failure may indicate that the object has been changed since it was signed. If object integrity is the issue, do not change the QVFYOBJRST system value or perform other actions that might allow the questionable object to restore. Doing so can circumvent the security that signature verification provides and allow a harmful object onto your system. Instead, you need to contact the object signer to determine the appropriate action to take to resolve the problem. |