- The J2EE engine startup fails due to the UME service (com.sap.security.core.ume.service) not being initialized and the below error is logged in the trace files (default trace file, std_server<x> and dev_server<x>).
- This issue is valid only for J2EE servers with the R/3 server as the UME backend.
" FATAL: Critical shutdown with exit code  was requested due to [AS Java cannot be started; core service [com.sap.security.core.ume.service] failed to start] CSN Component [BC-JAS-SEC-UME], DC Name [sap.com/com.sap.security.core.ume.service] com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (103) Caused by: com.sap.conn.rfc.exceptions.RfcGetException: JCO_ERROR_LOGON_FAILURE: User account not in validity date on localhost sysnr <nr> Return code: RFC_SYS_EXCEPTION(3)"
- Release Independent
- SAP NetWeaver
SAPJSF J2EE_GUEST ,SAP Production ERP SRM CRM ERP PPM SEM APO XI PI PORTAL issue UME expired client SU01 logon data valid from valid through configtool cluster_data Propertysheet com.sap.security. core.ume.service destinations Propertysheet UMEBackendConnection Connection and Transport , KBA , BC-JAS-SF , Startup Framework , BC-JAS-SEC-UME , User Management Engine , 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.