J2EE Failed to start , after changing UME datasource

[Former Member]

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

[Former Member · Accepted solution]

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.

[Former Member · Accepted solution]

Hello Amol ,

you are correct I am having Java+ABAP stack , as per your instrauction i have change configuration file to dataSourceConfiguration_r3.xml and restart server .

Please check log after restarting server ..

Apr 19, 2006 3:41:03 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_69] 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: "'ashost' is missing". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{

receiverid_guest=master

poolmaxsize=10

receiverid=master

}

".

Apr 19, 2006 3:41:03 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_69] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

Apr 19, 2006 3:41:03 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_69] Fatal:

Apr 19, 2006 3:41:03 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_69] 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'!: '<b>ashost</b>' is missing

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'!: 'ashost' is missing

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

Regards,

Santosh

[Former Member · Accepted solution]

Hi Santosh,

o Open Config Tool and navigate to "cluster-data->Global server configuration->services" and select the service "com.sap.security.core.ume.service".

o Update the key "ume.r3.connection.master.ashost"with the saprouter string.

NOTE: master is the default connection block. Change the property in the appropriate block (001, 002, 003 etc), if the default connection block is changed.

o Restart the J2EE standalone instance after the changes.

Thanks,

Samta

[Former Member · Accepted solution]

Hi Santosh,

Just to simplify my previous reply -

Simply Update the key "ume.r3.connection.master.ashost" with the hostname of your portal server.

Thanks,

Samta

[Former Member · Accepted solution]

Hello Amol / Samta ,

After specifying ume.r3.connection.master.ashost , client , synr ,user, password & creating Guest account in R/3 System J2EE and Poratal is running .

I am using dataSourceConfiguration_r3.xml as a datasource . while accessing EP Poratal using J2EE_ADMIN account i am not able to access Portal content .

" No portal roles are assigned for this user.If this problem persists, contact your system administrator. "

I am also not able to acess J2EE Vis. Admin using user J2EE_ADMIN while i can access the same using SAP*

Any clue ?

Regards,

Santosh

Message was edited by: Santosh Karadkar

[Former Member · Accepted solution]

Hi Santosh,

It seems that j2ee_admin is not having super_admin role. For this perform the following steps:

1 Start the UME administration console (http://<host>:<port>/useradmin).

2 Log on with the administrator user (for example J2EE_ADMIN).

3 Choose 'Roles' and search for the super_admin role.

4 Assign this role to j2ee_admin user.

After this, you are able to logonto EP 6.0 (http://<host>:<port>/irj) with your administrator user and this user has super administrator permissions.

With regards,

Amol

[Former Member · Accepted solution]

Hello Amol ,

Thanks for your kind co-operation, I have already check with UME administration console but unfortunately I am getting message while accessing the page (Application cannot be started.

Details: com.sap.engine.services.deploy.container.ExceptionInfo: Naming error. )

what is procedure to assign ABAP user to access Portal ? Where can i get any Doc on that ?

Thanks in Advance .

Regards,

Santosh

[Former Member · Accepted solution]

Hi Santosh,

u can activate the emergency user "sap*" by following

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm</a>

then assign the required role to j2ee_admin user.

With regards,

Amol

[Former Member · Accepted solution]

Hello Amol,

thank you very much for your kind support !

Issue is get resolved .....

Regards,

Santosh

[Former Member · Accepted solution]

Hi Santosh,

For post installation guide of EP 7 u can try out following links:

https://service.sap.com/installnw2004s

https://service.sap.com/instguidesNW2004s

with regards,

Amol.

[Former Member]

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

[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