Symptom
- SPAM/SAINT is stuck in DD Activation phase for quite some time and there is no apparent error in the tool.
- Checking the SLOG file you see entries similar to the following:
ERROR: The following call returned with exit code 213:
ERROR: sapevt SAP_TRIGGER_RDDIMPDP name=<SID> tpsid=<SID> -t
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. YYYYMMDDHHmmss :
ERROR: The following call returned with exit code 213:
ERROR: sapevt SAP_TRIGGER_RDDIMPDP name=<SID> tpsid=<SID> -t
ERROR: Background jobs cannot be started.
ERROR: Please check trace file dev_evt.
WARNING: (This warning is harmless if no further warnings follow.)
- In dev_evt trace on one of the application server's work directory you can find similar error:
*** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/<SID>/D00/exe/libsapcrypto.so") FAILED
"/usr/sap/<SID>/D00/exe/libsapcrypto.so: cannot open shared object file: No such file or directory" [dlux.c 550]
*** ERROR => ssfPkiInitSAPCryptolib: SsfSupInitEx("/usr/sap/<SID>/D00/exe/libsapcrypto.so")==10 (SSF_SUP_NOLIB) [ssfxxpki.c 209]
*** ERROR => ssfPkiInitSAPCryptolib: FAILED to load SAPCRYPTOLIB -- ssfPKI functions unavailable! [ssfxxpki.c 258]
PKI library initialization failed
Read more...
Environment
SAP NetWeaver - All releases
Product
Keywords
SAINT, Dictionary, Activation, SPAM, Update, Installation queue, Import , KBA , BC-UPG-OCS , Online Corr. Support (Tools:Supp.-Pack., Addon Install/Upgr) , BC-UPG-ADDON , Upgrade Add-On Components , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview