J2EE Start Failed after upgrade on SP11

[Former Member]

Hello SDN members,

I have this problem since I upgrade SP11 for EP, UME...

Apr 11, 2007 8:46:07 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_46] 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

lang=EN

}

".

Apr 11, 2007 8:46:07 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_46] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

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

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.core.persistence.datasource.PersistenceException: 'ashost' is missing

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

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

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

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

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.core.persistence.datasource.PersistenceException: 'ashost' is missing

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

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

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

... 6 more

What is the problem ? UME Configuration has deleted ? I have to reconfigure it ?

Best regards

and thanks for your helps !

[Former Member]

Yo dont you just love people who say they resolved the issue and do not give the results after you have people taking time out to try and help them good job!! I had the same problem and I resolved it by generating the role for SAPJSF SAP_BC_JSF_COMMUNICATION_RO and making him a communication user.

Mike

[Former Member]

Hi,

It seems to be that the ABAP configuration is missing or not correct. To configure it please, follow the steps.

Goto configtool which will be located in

C:\usr\sap\<SID>\JC<Number>\j2ee\configtool\confitool.bat

Open the property sheet

com.sap.security.core.ume.service and configure the following properties.

1.ume.persistance.data_source_configuration = dataSourceConfiguration_abap.xml

2. r3.connection.master.ashost = R/3 system host value

3. r3.connection.master.client = R/3 system client id

4.r3.connection.master.sysnr = R/3 system number

(To get the above parameters values, login to the backend system, go to "system"

and click "Status". This will give values for the above parameters).

5.r3.connection.master.user = R/3 system communication user

6.r3.connection.master.password = R/3 system communication user password

(it is the password of the communication user which is in the backend system)

7. ume.login.guest_user.uniqueids : Guest userid created in the backend system

8. login.ticket_portalid : yes (If administrator id length is more than 12 charcters ex: administrator)

: No (If administrator id length is less than 12 charcters ex: j2ee_admin)

These are all the configurations for ABAP persistence.

Reward with suitable points....

Thanks

R.Murali

[Former Member]

Hello,

Thans a lot... Errors of UME are resolved. Now I have another problem !

#1.5#00123F744AA900200000000000000D7000042DEC62FB021B#1176393203000#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_52##0#0#Fatal#1#com.sap.security.core.persistence#Java#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: "". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "".##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: "". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "".#2#User SAPJSF has no RFC authorization for function group SYST

It's amazing that I need to reconfigure all with this upgrade... Grr...

Thanks in advance for yout help !

Best regards,

[daniel_davinci]

Hi ,

It clearly appears to be an issue with the authorisations of the SAPJSF user in the backend.

Have you checked the users authorisations in the backend?

It should have:SAP_BC_JSF_COMMUNICATION role or the corresponding role-profile assigned

This needs to be in client 001.

Read more here: http://help.sap.com/saphelp_nw04/helpdata/en/d6/225f3ce4dd3370e10000000a114084/frameset.htm

Cheers

Daniel

[Former Member]

Well Thanks Daniel, this error has been resolved but now I have that !

1.5#00123F744AA9001000000001000012A000042DED6C9F0D8A#1176397659703#/System/Security##com.sap.caf.eu.gp.mail.cf.core.service.impl.AbstractMailCFServiceFrame#######SAPEngine_System_Thread[impl:5]_67##0#0#Info#1#com.sap.caf.eu.gp.mail.cf.core.service.impl.AbstractMailCFServiceFrame#Plain###Mail CF Service is starting up. #

#1.5#00123F744AA9001000000003000012A000042DED6CA29FE6#1176397659937#/System/Security##com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#######SAPEngine_System_Thread[impl:5]_67##0#0#Info#1#com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#Plain###IMailCFService registered successfully in JNDI.#

#1.5#00123F744AA9001000000005000012A000042DED6CA42AE0#1176397660046#/System/Security##com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#######SAPEngine_System_Thread[impl:5]_67##0#0#Warning#1#com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#Plain###createSubcontext operation failed; context sap.com already exists.#

#1.5#00123F744AA9001000000007000012A000042DED6CA42D26#1176397660046#/System/Security##com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#######SAPEngine_System_Thread[impl:5]_67##0#0#Warning#1#com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#Plain###createSubcontext operation failed; context com.sap.nw.eu.gp already exists.#

#1.5#00123F744AA9001000000009000012A000042DED6CA434E7#1176397660046#/System/Security##com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#######SAPEngine_System_Thread[impl:5]_67##0#0#Info#1#com.sap.caf.eu.gp.mail.cf.core.registration.impl.JNDIRegistration#Plain###IMailCFGatewayFactory registered successfully in JNDI.#

#1.5#00123F744AA900100000000B000012A000042DED6CA45229#1176397660046#/System/Security##com.sap.caf.eu.gp.mail.cf.core.common.CoreThreadController#######SAPEngine_System_Thread[impl:5]_67##0#0#Info#1#com.sap.caf.eu.gp.mail.cf.core.common.CoreThreadController#Plain###Starting J2EE thread.#

#1.5#00123F744AA9001800000001000012A000042DED6CAB11F7#1176397660500#/System/Security##com.sap.caf.eu.gp.mail.cf.core.multithreading.TimerTask#######SAPEngine_Application_Thread[impl:3]_4##0#0#Info#1#com.sap.caf.eu.gp.mail.cf.core.multithreading.TimerTask#Plain###The timer task:com.sap.caf.eu.gp.mail.cf.core.multithreading.ResendMailTimerTask@1c9fe7e is started#

#1.5#00123F744AA9002000000000000012A000042DED6DDA6459#1176397680375#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_46##0#0#Info#1#com.sap.security.core.persistence#Java#User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) connected to client of ABAP backend system as user ##User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) connected to client of ABAP backend system as user #3#001#XXX#SAPJSF#

#1.5#00123F744AA9002000000001000012A000042DED6E04B6DE#1176397683140#/System/Security/Usermanagement##com.sap.security.core.persistence#######SAPEngine_System_Thread[impl:5]_46##0#0#Info#1#com.sap.security.core.persistence#Java#R3RoleDataSource representing backend roles as UME groups##R3RoleDataSource representing backend roles as UME groups##

#1.5#00123F744AA9002000000002000012A000042DED6F474A9B#1176397704281#/System/Security/Usermanagement##com.sap.security.core.server.ume.service.UMEServiceFrame#######SAPEngine_System_Thread[impl:5]_46##0#0#Info#1#com.sap.security.core.server.ume.service.UMEServiceFrame#Plain###UME Service initialized successfully#

#1.5#00123F744AA9002100000000000012A000042DED6F47A6C4#1176397704312#/System/Security##com.sap.engine.services.security#######SAPEngine_System_Thread[impl:5]_39##0#0#Info#1#com.sap.engine.services.security#Plain###IAIK.addAsJDK14Provider() OK#

#1.5#00123F744AA9002100000001000012A000042DED6F4C9403#1176397704640#/System/Security##com.sap.engine.services.security#######SAPEngine_System_Thread[impl:5]_39##0#0#Info#1#com.sap.engine.services.security#Plain###Userstore <UDDI> registered successfully.#

#1.5#00123F744AA9002100000003000012A000042DED6F4E144E#1176397704734#/System/Security/UserStoreUME##com.sap.security.core.server.userstore.UserContextUME#######SAPEngine_System_Thread[impl:5]_39##0#0#Error#1#/System/Security/UserStoreUME#Java###Error while trying to get the anonymous user: #1#Cannot find first configured anonymous user: Guest: USER_AUTH_FAILED: User account for logonid "Guest" not found!#

#1.5#00123F744AA9002100000005000012A000042DED6F4E2A17#1176397704734#/System/Security##com.sap.engine.services.userstore.UserContext.<init>(UserContextSpi, Properties)#######SAPEngine_System_Thread[impl:5]_39##0#0#Fatal#1#com.sap.engine.services.userstore#Plain###Can not instantiate UserContext with given properties.#

#1.5#00123F744AA9002100000008000012A000042DED6F4EF6B5#1176397704781#/System/Security##com.sap.engine.services.security#######SAPEngine_System_Thread[impl:5]_39##0#0#Error#1#com.sap.engine.services.security#Java#security_0001#com.sap.engine.services.security.exceptions.SecurityResourceBundle#Unexpected exception:##

[Former Member]

OK I resolved the problem myself.

Thanks for your answers !

I give you reward points in feedback.

Best regards.

[Former Member]

Problem resolved.