SAP was up and running for some time, without presenting the issue.
One of the following symptoms started to be observed:
- Users were not able to logon due to a license related error;
- RFC entries (like tRFC entries - transaction SM58 - with destination "NONE") started to fail due to a license related error like.
Such license related error is usually "Logon not possible (error in license check)".
This happens despite that the system has a valid license (confirmed through the transaction SLICENSE).
The behavior can affect a single instance.
- Product independent
- Release independent
- Client/Server Technology - License
SAPSECULIB, SAPCryptoLib, CommonCryptoLib, DLENOACCESS, DlLoadLib()==DLENOACCESS, Could not load SSF library, 138 likey_init, Could not initialize the SAPSECULIB, SAPlicense, LIKEY initialisation failed , KBA , BC-CST-SL , SAP License , BC-SEC , Security - Read KBA 2985997 for subcomponents , BC-CST , Client/Server Technology , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.