1853913 - Unique name already exists leads to SAP J2EE engine crash | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

1853913 - Unique name already exists leads to SAP J2EE engine crash

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>):
********************************************************************************************************************************************
Fatal: Initialization of <UME DETAILS> data source (com.sap.security.core.persistence.datasource.imp) failed: Technical details: User with unique name <<user name>> already exists: at com.sap.security .core.server .ume.service.UMEService Frame.start(UMEServiceFrame.java:)Caused by: com.sap.security.api.UserAlreadyExistsException. FATAL: Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [com.sap.security.core.ume.service] failed to start]
********************************************************************************************************************************************


Read more...

Environment

  • Release Independent
  • SAP NetWeaver

Product

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

Keywords

com.sap.security.core.persistence.datasource, emergency user, 718383, 1061405 , http://scn.sap.com/docs/DOC-23182, Change UME, J2EE_ADMIN, J2EE_GUEST, UserAlreadyExistsException, fatal, stopped , 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.