Server node stopped with Error 5, Dispatcher running

[Former Member]

Hello Experts,

In a Dual stack system.

In Java Engine Server node is stopped with Error 5, but the Dispatcher is running.

And the state of Jcontrol is : Some processes running

I analysed the default trace file it is showing Error:

"Critical Shutdown was invoked, Reason is : Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started."

I also checked security.0.log file, and I found error:

"Start of UME Service failed. Check help topic "Start of UME SErvice failed". Technical Details: Name or Password is incorrect {repeat logon}".

Do I need to maintain passwod some where ?

What could be the problem please suggest. As its a Production.

Regards,

Amit

[Former Member]

Thanks Steven

The user indeed is SAPJSF.

Apologies for the oversight.

Regards

Javed

[Former Member]

Did you change the J2EE_ADMIN user password recenlty??

In the above two parameters, put master user as J2EE_ADMIN and the password as whatever the J2EE_ADMIN user has in the ABAP client connected to the Java engine . By Default it is 001

Cheers!!!

Javed

[former_member227283]

Hi Amit,

You have to login to Configtools, where in configtools you have to goto Cluster-data -> Instance -> Server -> services.

where as in services you will get service with name -> com.sap.security.core.ume.service.

Once you click on above paremeter you will get parameter list on right side , where you have to maintain user in parameter

ume.r3.connection.master.user =

ume.r3.connection.master.passwd =

Once above 2 parameter is maintained, restart the applciation, this step should resolve your problem.

Thanks

Anil

[Former Member]

Hi,

I had this problem last week. Anil's advice is correct - check that these user details are maintained in the config tool.

However, also check that this user ID is not locked and that the password is the same as stored in the config tool. In my case, I checked the ABAP side of the dual-stack system and found that we'd accidently locked the user ID (in my case the user ID used was SAPJSF).

Hope this helps.

Steve.

[Former Member]

Hi,

Thanks Steven, Javed & Anil. Yes finally I found that the user is locked and user name is same as SAPJSF.

We have requested customer to reset the password in ABAP side, and will maintain the same in configtool.

Thanks to all for your help.

Regards,

Amit