How To Fix SLIC214 - Could not read digitally-signed licenses

SAP Error Message - Details

• Message type: E = Error

• Message class: SLIC - saplicense Messages

• Message number: 214

• Message text: Could not read digitally-signed licenses

What causes this issue?

The system could not read the digitally-signed license keys from the
database. Since the signature is checked when reading the license keys,
they need to be read by the SAP kernel. You therefore need to check the
SAP kernel for the cause of the problem.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check which error occurred in the SAP kernel. To do this, search the
work process kernel trace files dev_w* for corresponding error messages.
You can identify the messages by the fact that they contain the name
"likey".
The most common cause is that the system could not load certain kernel
libraries. You can see this from the following messages in the kernel
trace files:
<NP>M *** ERROR => likey_init: Could not initialize the SAPSECULIB by
calling SsfLibGetToolkit (). [sliclikey.c 1314]</>
<NP>M *** ERROR => SlicLikeyInit: likey_init failed: 1 [sliclikey.c
261]</>
<NP>M *** ERROR => SAPlicense: LIKEY initialisation failed! [slicshm.c
293]</>
In this case, refer to SAP Note 982056, and check the installation of
libsapsecu or libsapcrypto.
If the messages in dev_w* do not help you to correct the problem, create
a support message for component BC-SEC. Add the messages from the dev_w*
trace files that are relevant to the problem, as described above, to the
support message.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SLIC214 - Could not read digitally-signed licenses ?

  The SAP error message SLIC214: Could not read digitally-signed licenses typically indicates an issue with the digital signature of the license files in your SAP system. This error can arise due to various reasons, including corrupted license files, issues with the SAP kernel, or problems with the configuration of the license management.
  Causes:
  
  Corrupted License Files: The license files may be corrupted or improperly formatted.
  Incorrect File Permissions: The SAP system may not have the necessary permissions to read the license files.
  Incompatible SAP Kernel: The version of the SAP kernel may not be compatible with the license files.
  Missing or Misconfigured License Files: The required license files may be missing or not correctly configured in the system.
  Digital Signature Issues: The digital signature of the license file may not be valid or recognized.
  
  Solutions:
  
  
  Check License Files:
  
  Verify that the license files are present in the correct directory (usually in the usr/sap/<SID>/SYS/global/ directory).
  Ensure that the license files are not corrupted. You may need to re-download the license file from the SAP Service Marketplace.
  
  
  
  File Permissions:
  
  Check the permissions of the license files to ensure that the SAP system has read access. You can use commands like ls -l in Unix/Linux to check permissions.
  Adjust permissions if necessary using chmod or chown.
  
  
  
  Update SAP Kernel:
  
  Ensure that you are using a compatible version of the SAP kernel. If necessary, update the kernel to the latest version that is compatible with your SAP system.
  
  
  
  Reconfigure License:
  
  If the license files are missing or misconfigured, you may need to reconfigure the license in the SAP system. This can often be done through transaction code SLICENSE.
  Use the SLICENSE transaction to upload a new license file if needed.
  
  
  
  Check Digital Signature:
  
  If the digital signature is the issue, ensure that the license file is obtained from a trusted source and is not tampered with. If necessary, contact SAP support for assistance.
  
  
  
  SAP Support:
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance. They can provide more specific guidance based on your system configuration and logs.
  
  
  
  Related Information:
  
  Transaction Code: Use transaction code SLICENSE to manage and check the status of your licenses.
  SAP Notes: Check for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to the official SAP documentation for license management for more detailed information on handling licenses and related errors.
  
  By following these steps, you should be able to resolve the SLIC214 error and ensure that your SAP system can read the digitally-signed licenses correctly.