Skip to Content
avatar image
Former Member

J2EE Failed to start , after changing UME datasource

Hello ,

After changing UME datasource in EP , J2EE failed to start .

I have also confirmned the all paramenter reffering

http://help.sap.com/saphelp_nw04s/helpdata/en/20/361941edd5ef23e10000000a155106/content.htm

Log entries in std_server0.out

Apr 19, 2006 1:21:24 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Connect to message server host failed

Connect_PM TYPE=B MSHOST=Q4INPUSY006 GROUP=SAP_J2EE_ADMIN R3NAME=IJA MSSERV=sapmsIJA PCS=1

ERROR Group SAP_J2EE_ADMIN not found

TIME Wed Apr 19 13:21:24 2006

RELEASE 700

COMPONENT LG

VERSION 5

RC -6

MODULE lgxx.c

LINE 4288

DETAIL LgIGroupX

COUNTER 1

". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{

passwd=********

receiverid=master

gwhost=Q4INPUSY006

client=100

poolmaxsize=10

mshost=Q4INPUSY006

user=J2EE_ADMIN

r3name=IJA

receiverid_guest=master

ashost=Q4INPUSY006

group=SAP_J2EE_ADMIN

}

".

Apr 19, 2006 1:21:24 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_71] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

Apr 19, 2006 1:21:24 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_71] Fatal:

Apr 19, 2006 1:21:24 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_71] Fatal:

service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: < Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: [] > : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:460)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Connect to message server host failed

Connect_PM TYPE=B MSHOST=Q4INPUSY006 GROUP=SAP_J2EE_ADMIN R3NAME=IJA MSSERV=sapmsIJA PCS=1

ERROR Group SAP_J2EE_ADMIN not found

TIME Wed Apr 19 13:21:24 2006

RELEASE 700

COMPONENT LG

VERSION 5

RC -6

MODULE lgxx.c

LINE 4288

DETAIL LgIGroupX

COUNTER 1

at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:367)

... 6 more

com.sap.engine.frame.ServiceException: < Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: [] > : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:460)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Connect to message server host failed

Connect_PM TYPE=B MSHOST=Q4INPUSY006 GROUP=SAP_J2EE_ADMIN R3NAME=IJA MSSERV=sapmsIJA PCS=1

ERROR Group SAP_J2EE_ADMIN not found

TIME Wed Apr 19 13:21:24 2006

RELEASE 700

COMPONENT LG

VERSION 5

RC -6

MODULE lgxx.c

LINE 4288

DETAIL LgIGroupX

COUNTER 1

at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:367)

... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Apr 19, 2006 1:21:24 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_71] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Thanks in advance ....

Regards,

Santosh

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Apr 19, 2006 at 09:38 AM

    Hi Santosh,

    I suppose u r having Java + ABAP stack.

    So change configuration file to

    "dataSourceConfiguration_r3.xml", because for Java + ABAP stack default UME datasource is ABAP.

    Then restart the server.

    Let me know if it doesnt work.

    with regards,

    Amol.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 19, 2006 at 08:28 AM

    Hi Santosh,

    It clearly shows that you must have configured your UME settings incorrectly.

    However, your server can be started. No issue in that.

    Logon to the portal server. In the configtool offline editor, Change to edit mode.

    Navigate to cluster_data -> server - > cfg -> services -> propertysheet com.sap.security.core.ume.service ->

    Change to Edit mode. Right on the proertysheet -> Change.

    Select "restore default" Now,the default configuration file for UME becomes dataSourceConfiguration_database_only.xml

    Restart your J2EE engine now.

    Thanks,

    Samta

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Samta ,

      Thnaks for your prompt reply ,

      Earlier I have also check with default parameter .. but no success ...

      Still i had again switch UME to access dataSourceConfiguration_database_only.xlm ..

      Please checlk the log after resotoring defaults .

      Core service security failed. J2EE Engine cannot be started.

      com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:

      at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:179)

      at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

      at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

      at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

      at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

      at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

      Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: Anonymous principal not configured

      at com.sap.engine.services.security.login.SecurityContext.setAnonymousPrincipal(SecurityContext.java:513)

      at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:139)

      ... 5 more

      Caused by: com.sap.security.core.server.userstore.UserstoreException: Could not get user Guest

      at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:196)

      at com.sap.engine.services.security.userstore.context.UserContext.getUserInfo(UserContext.java:102)

      at com.sap.engine.services.security.login.SecurityContext.setAnonymousPrincipal(SecurityContext.java:507)

      ... 6 more

      Caused by: com.sap.security.api.NoSuchUserAccountException: USER_AUTH_FAILED: User account for logonid "Guest" not found!

      at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:381)

      at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:56)

      at com.sap.security.core.imp.UserAccountFactory.getReadonlyUserAccountByLogonId(UserAccountFactory.java:672)

      at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:474)

      at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:460)

      at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:722)

      at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:708)

      at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:192)

      Logs are directly indicating "USER_AUTH_FAILED: User account for logonid "Guest" not found!"

      I have manually create J2EE_GUEST user in R/3 System still no chenge ..

      Is there any other related changes that i have to monitor ?

      Regards,

      Santosh