1603769 - sysnr is missing: SAP JAVA startup issue | SAP Knowledge Base Article

SAP Knowledge Base Articles - preview

1603769 - sysnr is missing: SAP JAVA startup issue


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>):

Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "'sysnr' is missing". This message is critical if it appears during the startup of the AS Java. Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started. com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed.



  • SAP Release Independent
  • SAP NetWeaver


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


jcmon, instance startup, SAP MMC, SMICM ,SAP Production ERP SRM CRM ERP PPM SEM APO XI PI PORTAL issue ume.r3.connection.master.sysnr ume.r3.connection.master.ashost , KBA , BC-JAS-SF , Startup Framework , 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.