Start of UME Logon Failed

[Former Member]

Dear Experts,

I know it is the most common error and I have searched and have done whatever I could. Kindly have a look and suggest your opinion on this issue.

Whenever I am starting my JAVA server, server0 is failing with error messages. When I am checking the logs in std_server0.out I find this log

I know the first impression is that SAPJSF is locked or not correct or does not match with Config tool parameter in Global Server Configuration

1.    I have made sure that SAPJSF is not locked in the 010 Client and reset the password.

2.     I have made sure that I have updated the saved password in ume.r3.connection.master.password

3. I have made sure that      ume.r3.connection.master.group is correct and exist in SMLG,

4. msghost is also correct

5. ume.r3.connection.master.user is SAPJSF

6. I dont know Administrator password, I have reset the sap* password and trying to log in Visual Admin, but it is not logging in from sap* also. I cant change Administrator password. and as Portal is not up cant even login to change Administrator password.

I also know that it is actually going and hitting the SAPJSF user in 010 client as after many restarts finally the SAPJSF user was locked due to many attempts.

But I am just not able to correct this error. Please help with any other suggestions or what should i try.

1. Can I create another communication user and try ?

2. Can i point it to another client and see ?

--------------------------------------------------------------------------------

stdout/stderr redirect

--------------------------------------------------------------------------------

node name   : server0

pid         : 18190

system name : AJQ

system nr.  : 38

started at  : Wed Jan 29 16:17:19 2014

[Thr 182894043296] Wed Jan 29 16:17:20 2014

[Thr 182894043296] MtxInit: 10001 0 0

SAP J2EE Engine Version 7.01   PatchLevel 58805. is starting...

Loading: LogManager ... 429 ms.

Loading: PoolManager ... 3 ms.

Loading: ApplicationThreadManager ... 1.111: [GC 1.111: [ParNew: 409600K->2039K(512000K), 0.0137560 secs] 409600K->2039K(1994752K), 0.0139240 secs] [Times: user=0.03 sy

s=0.00, real=0.02 secs]

105 ms.

Loading: ThreadManager ... 28 ms.

Loading: IpVerificationManager ... 9 ms.

Loading: ClassLoaderManager ... 15 ms.

Loading: ClusterManager ... 156 ms.

Loading: LockingManager ... 59 ms.

Loading: ConfigurationManager ... 1522 ms.

Loading: LicensingManager ... 22 ms.

Loading: CacheManager ... 127 ms.

Loading: ServiceManager ...

Loading services.:

  Service DQE started. (5 ms).

  Service caf~eu~odi~mnuacc started. (1 ms).

  Service memory started. (61 ms).

  Service cross started. (52 ms).

  Service file started. (65 ms).

  Service timeout started. (51 ms).

  Service runtimeinfo started. (32 ms).

  Service caf~eu~cc~api started. (27 ms).

  Service userstore started. (8 ms).

  Service trex.service started. (52 ms).

  Service jmx_notification started. (16 ms).

  Service p4 started. (142 ms).

  Service classpath_resolver started. (15 ms).

5.993: [GC 5.993: [ParNew: 411639K->16290K(512000K), 0.0446250 secs] 411639K->16290K(1994752K), 0.0448620 secs] [Times: user=0.19 sys=0.04, real=0.05 secs]

  Service log_configurator started. (3673 ms).

  Service locking started. (4 ms).

  Service http started. (151 ms).

  Service naming started. (297 ms).

  Service failover started. (40 ms).

  Service appclient started. (55 ms).

  Service javamail started. (83 ms).

  Service ts started. (78 ms).

  Service jmsconnector started. (97 ms).

  Service licensing started. (8 ms).

  Service connector started. (143 ms).

  Service iiop started. (141 ms).

  Service webservices started. (357 ms).

  Service deploy started. (4479 ms).

  Service com.sap.portal.runtime.config.kmreadonly started. (6 ms).

  Service configuration started. (18 ms).

  Service MigrationService started. (26 ms).

  Service bi~mmr~deployer started. (6 ms).

  Service dbpool started. (710 ms).

  Service UT started. (5 ms).

  Service caf~eu~gp~mail~cf started. (35 ms).

10.099: [GC 10.099: [ParNew: 425863K->28588K(512000K), 0.0474310 secs] 425863K->28588K(1994752K), 0.0476180 secs] [Times: user=0.23 sys=0.05, real=0.05 secs]

Jan 29, 2014 4:17:31 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_69] Fatal: Initialization of ABAP data source (com.sap.security.core.

persistence.datasource.imp.R3Persistence) failed: "Name or password is incorrect (repeat logon)". This message is critical if it appears during the startup of the AS Ja

va.

Jan 29, 2014 4:17:31 PM  ...re.server.ume.service.UMEServiceFrame [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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (re

peat logon)

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

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)

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

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

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

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

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

        ... 6 more

com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (re

peat logon)

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

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

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

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect (repeat logon)

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

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

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

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

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

        ... 6 more

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

Jan 29, 2014 4:17:31 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com

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

Heap

par new generation   reserved 614400K, committed 614400K, used 49248K [0x0000000041460000, 0x0000000066c60000, 0x0000000066c60000)

  eden space 409600K,   5% used [0x0000000041460000, 0x000000004288d208, 0x000000005a460000)

  from space 102400K,  27% used [0x0000000060860000, 0x000000006244b068, 0x0000000066c60000)

  to   space 102400K,   0% used [0x000000005a460000, 0x000000005a460000, 0x0000000060860000)

concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x0000000066c60000, 0x00000000c1460000, 0x00000000c1460000)

concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 43020K [0x00000000c1460000, 0x00000000e1460000, 0x00000000e1460000)

[Former Member]

Dear All, 

I know all this, I have mentioned that I have checked all this things already. SAPJSF is not locked and i am putting correct password in config tool which is there in ABAP Client 010 I also know how to enable sap* i have done that.

2 things now:

1.     Even after putting correct password for SAPJSF in ABAP CLNT 010 and Config tool it is not working. CLient number system name everything is correct in config tool.

2.     My Portal is down, I cant login to User Admin, I have activated sap* --- Now how to change administrator password when I cant login to Visual Admin(even with sap* and cant login to user admin) ???

I would be grateful if someone can reply on this

[Reagan]

Upload the latest default trace please.

Regards

RB

[Former Member]

Rajat Sharma wrote:
Now how to change administrator password when I cant login to Visual Admin(even with sap* and cant login to user admin) ???

go to http://<portal.url>:<port>/useradmin

log in with SAP* and change a password for administrator user

[Former Member]

Hello Rajat

There is no point in trying to change the Administrator password. The reason of J2EE Engine failure is wrong setup of SAPJSF password. You cannot change administrator password when J2EE Engine is not running. May be you can do that by directly changing it in the ABAP datasource, but it is not advisable. Even if you do that, there will be no impact on starting up of the java engine as it is not the root cause here.

1. Ensure that the sapjsf user is not locked, and that the user can authenticate to the ABAP system with the currently defined password If not, reset the password.

2. Ensure that the password that the J2EE Enigne is using is correct and sysnched with that defined in the ABAP system:
-  open Config Tool and go to cluster-data -> Global Server onfiguration-> Services

  -> com.sap.security.ume.service. -Select the property ume.r3.connection.master.passwd
  and setup the proper password there.
-  Save the changes.

-  After that please go to cluster-data -> instance_IDxxxxxx -> server_IDxxxxxx50 -> Sevices

  ->com.sap.security.ume.service
-  You should not see any Local configurations there. But if any configuration incidently occurs

   here, please select it and press the button "Restore to global".
-  If you have more than one server node under instance_IDxxxxxx, please check if there is any local

  properties in com.sap.security.ume.service

3. Start the configtool, switch to configuration editor mode and expand cluster_data -> server

    cfg -> services -> Propertysheet.com.sap.security.core.ume.service -> click on this

    and check if there is a value specified for ume.r3.connection.master.passwd

    You may delete and re-enter the value.

4. save the changes and restart the engine.

Thanks,

Tapan

[Asha_Pillai]

Hello,

Please check if the following parameters are set correctly in configtool(You have already checked few of them)

Please go to Config Tool -> template - -> servcies ->
com.sap.security.core.ume.service
Find and adjust values for below parameters:

   ume.r3.connection.master.ashost
   ume.r3.connection.master.sysnr
   ume.r3.connection.master.client
   ume.r3.connection.master.user
   ume.r3.connection.master.passwd

Regards,

Asha

[nirmal_konchada]

Jan 29, 2014 4:17:31 PM  ...re.server.ume.service.UMEServiceFrame [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: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Name or password is incorrect (re
peat logon)
        at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)

The error that your are see is purely related to SAPJSF and its correct password in configtool.

and if you want to use SAP* to login then you need to activvate the emergency user in the java stack using below link

http://help.sap.com/saphelp_nw2004s/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/content.htm

Kindly make sure you enter the correct password in the properties and save. Then take a restart of the system and check.

Regards,

Nirmal

[Former Member]

Hi,

In order to activate SAP* on Java stack follow these steps.

1. Start configtool.

2. Choose "Switch to configuration editor"

3. On the "Display Configuration" tab choose: cluster_config - system - custom_global - cfg - services - com.sap.security.core.ume.service - Propertysheet properties

4. Choose "Switch between view and edit mode".

5. Choose  Edit the details of the selected node.

6. Edit ume.superadmin.activated and ume.superadmin.password parameters.

7. Apply your changes

8. Restart the AS Java.

Regarding your problem - make sure that SAPJSF password is set correctly.

Also make sure that SAPJSF user type is set to "System" on backend.

[Former Member]

Hi,

Just one confirmation please. SAPJSF should be set as communication user or System user ?

[former_member185239]

Hi Rajat ,

Try to keep the same password of SAPJSF , in 001 client and point the client to 001

Restart the system.

With Regards

Ashutosh Chaturvedi

[Reagan]

Hello

If the UME for the portal is an ABAP stack then you need to do the user administration tasks at the ABAP side.

First check whether the SAPJSF user is locked.

If you have changed the password for the user SAPJSF then update that in the configtool.

Regards

RB