1625402 - Config file is null: SAP startup issue | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

1625402 - Config file is null: SAP startup issue

Symptom

The SAP Application Server JAVA 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>):

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started. com.sap.engine.frame.ServiceException: Config file is null! at com.sap.security.core.server.ume. service.UMEServiceFrame.start(UMEServiceFrame.java) at com.sap.security.core.persistence.datasource.imp.Configuration.<init> [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started


Read more...

Environment

  • SAP Netweaver
  • Release Independent

 

Product

SAP Composition Environment all versions ; SAP NetWeaver all versions ; SAP Process Integration all versions ; SAP Solution Manager all versions

Keywords

jcmon, instance startup, SAP MMC, SMICM ume.persistence.data_source_configuration 718383 cluster_data Propertysheet com.sap.security. core.ume.service , KBA , BC-JAS-SF , Startup Framework , BC-JAS-SEC-UME , User Management Engine , Problem

About this page

This 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.