Errors reported by the encryption manager
The encryption manager returns error messages related to encryption-enabled tape drives.
| Error Number | Description | Action |
|---|---|---|
| EE2D | Encryption Read Message Failure: Invalid Message Type | The key manager received a message out of sequence or received a message that it does not know how to handle. Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM® Representative). Enable debug on the key manager server. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE29 | Encryption Read Message Failure: Invalid signature | The message that was received from the drive or proxy server does not match the signature on it. Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Enable debug on the key manager. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE2E | Encryption Read Message Failure: Internal error: Invalid signature type | The message that was received from the drive or proxy server does not have a valid signature type. Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Enable debug on the key manager. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE23 | Encryption Read Message Failure: Internal error: "Unexpected error........" | The message that was received from the drive or proxy server might not be parsed because of general error. Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Enable debug on the key manager server. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE02 | Encryption Read Message Failure: DriverErrorNotifyParameterError: "Bad ASC & ASCQ received. ASC & ASCQ does not match with either of Key Creation/Key Translation/Key Acquisition operation." | The request is for an unsupported action. Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Check the versions of drive or proxy server firmware and update them to the latest release, if needed (see Updating drive firmware). Enable debug tracing on the key manager. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE2C | Encryption Read Message Failure: QueryDSKParameterError: "Error parsing a QueryDSKMessage from a device. Unexpected disk count or unexpected payload." | The request is for an unsupported function. Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Check the versions of drive or proxy server firmware and update them to the latest release, if needed (see Updating drive firmware). Enable debug tracing on the key manager. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE2B | Encryption Read Message Failure: Internal error: "Either no signature in DSK or signature in DSK cannot be verified." | Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Check the versions of drive or proxy server firmware and update them to the latest release, if needed (see Updating drive firmware). Enable debug tracing on the key manager. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE0F | Encryption logic error: Internal error: "Unexpected error. Internal programming error in key manager." | Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Check the versions of drive or proxy server firmware and update them to the latest release, if needed (see Updating drive firmware). Enable debug tracing on the key manager. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |
| EE01 | Encryption Configuration Problem: "Drive not configured." | The drive that is trying to communicate with the key manager is not present in the drive
table. Ensure that the config.drivetable.file.url is correct in the
KeyManagerConfig.properties file, if that parameter is supplied. Run the
listdrives command to check whether the drive is in the list. If not, configure the
drive manually by using the adddrive command with the correct drive information or
turn "auto-fill" ON by setting drive.acceptUnknownDrives to true using the
modconfig command. Enable debug tracing and try the operation again. If the problem
persists, contact IBM Support. |
| EE25 | Encryption Configuration Problem: Errors that are related to the drive table occurred. | Ensure that the config.drivetable.file.url is correct in the
KeyManagerConfig.properties file, if that parameter is supplied. Run the
listdrives -drivename <drivename> command on the key manager to verify whether
the drive is correctly configured (for example, the drive serial number, alias, and certifications
are correct). Ensure that you are running the latest version of the key manager (to determine the
latest version, contact your IBM Representative). Check the versions of drive or proxy server
firmware and update them to the latest release, if needed (see Updating drive firmware). Enable debug tracing and try the operation again. If the
problem persists, contact IBM Support. |
| EE31 | Encryption Configuration Problem: Errors that are related to the keystore occurred. | Check the key labels that are used or configured for the defaults. Run the listdrives
-drivename <drivename> command on the key manager to verify whether the drive is
correctly configured (for example, the drive serial number, alias, and certifications are correct).
Ensure that you are running the latest version of the key manager (to determine the latest version,
contact your IBM Representative). Check the versions of drive or proxy server firmware and update
them to the latest release, if needed (see Updating drive firmware). Enable debug
tracing and try the operation again. If the problem persists, contact IBM Support. |
| EEE1 | Encryption logic error: Internal error: "Unexpected error: EK/EEDK flags conflict with subpage." | Ensure that you are running the latest version of the key manager (to determine the latest version, contact your IBM Representative). Check the versions of drive or proxy server firmware and update them to the latest release, if needed (see Updating drive firmware). Enable debug on the key manager. Try to re-create the problem and gather debug logs. If the problem persists, contact IBM Support. |