Troubleshooting
Problem
com.ibm.ecm.crypto.CipherException: System cannot generate 256‑bit keys
This error occurs when the Java runtime lacks the cryptography policy files required to generate 256‑bit keys. Update the Java version or install the appropriate Java Cryptography Extension (JCE) policy files as described in the linked technote.
com.ibm.ecm.crypto.CipherException: Failed to encrypt/decrypt
This error occurs when a data encryption key (DEK) is not encrypted with the current key encryption key (KEK) or when a secret is not encrypted using the current DEK. Resolve the issue by rotating the DEKs and then resetting the affected secrets.
Note: If you have a backup of the KEK, you can restore it as described in the following technote without rotating DEKs or resetting secrets.
Important: If the ICN configuration directory is not shared across all ICN servers, ensure each server uses the same KEK as described in the following technote.
1. Rotate the DEKs as described in the referenced technote. You may skip the final step because all ICN servers will be started later.
Note: The KEK does not need to be rotated.
2. Reset secrets by opening the ICN admin desktop, navigating to configuration pages that contain encrypted values (for example, the Task Manager administrator password), entering the new password, and saving the configuration.
3. Start all ICN servers.
com.ibm.ecm.crypto.CipherException: Failed to prepare material
Caused by: java.io.IOException: Unexpected number of data files found
This error occurs when the KEK directory (".ikm") in the IBM Content Navigator configuration directory contains unexpected files. Back up the directory, remove all extraneous files, restart the ICN server, and then address the earlier “Failed to encrypt/decrypt” error by rotating the DEKs.
com.ibm.ecm.crypto.CipherException: call failed
Caused by: java.nio.channels.OverlappingFileLockException
Upgrade to IBM Content Navigator 3.0.7 interim fix 1, 3.0.6 interim fix 4, 3.0.5 interim fix 8, or a later release.
Additional Note
Ensure the KEK is backed up and reused during every ICN upgrade. If a KEK is missing, ICN generates a new one that cannot decrypt existing DEKs.
Related Information
Document Location
Worldwide
[{"Business Unit":{"code":"BU056","label":"Miscellaneous"},"Product":{"code":"SSEUEX","label":"IBM Content Navigator"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF051","label":"Linux on IBM Z Systems"},{"code":"PF033","label":"Windows"}],"Version":"3.0.5 iFix 1 or later","Edition":"","Line of Business":{"code":"LOB18","label":"Miscellaneous LOB"}}]
Product Synonym
ICN
Was this topic helpful?
Document Information
Modified date:
12 September 2026
UID
ibm11120245