503 Service Unavailable, Dispatcher running, but no server connected

[Former Member]

Hi,

We have an XI Server at SP13.

My j2ee_admin was locked due to wrong inputs in password. So I was following "help.sap.com" and changed the UME properties. I tried loogin into Visual admin using sap* user that i have activated and i tried logging using Visual Admin and i got the following error.

Unable to Logon to Local Host

"End of Stream is reached unexpectedly during input from socket[addr=/10.1.1.13,port=50004,localport=3764].

Then restarted my J2EE Server Instance via SAPMMC. I could see my J2EE server running.I didnot change anything else via the Config Tool.

When i try to access it via the URL "http://10.1.1.13:50000/index.html", i get the following error.

503 Service Unavailable.

Dispatcher running, but no server connected!

Then i tried to logon to the J2EE Visual Administrator and i get the following error.

Unable to Logon to Local Host

"End of Stream is reached unexpectedly during input from socket[addr=/10.1.1.13,port=50004,localport=3764].

Cheers,

Siva Maranani.

[Former Member]

Hi Siva,

the error for the symptom is clear: The J2EE does not find the required service user with logon id "Guest". The solution would be, to change the value for the parameter ume.login.guest_user.uniqueids to an existing user (without any roles, see http://help.sap.com/saphelp_nw04/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/frameset.htm).

More tricky is the question, how it happened. Since you are running XI, you should normally have installed the J2EE with UM Datasource Configuration dataSourceConfiguration_r3_roles_db.xml. In this case, the name of the guest user is normally J2EE_GUEST (in UM Property). If this is the case, and you have simply a different value in the UM Property Sheet, you can change the value back to J2EE_GUEST (verify via su01 in the ABAP that this user exists). If you have installed with any different datasource configuration file, you would need to recheck, which datasource configuration file is suitable for you, and to which datasource configuration file you can change. In this case, I would recommend to carefully read note 718383.

Best regards,

Joerg

Hint: If your administrator user J2EE_ADMIN is locked, you can unlock the user via the ABAP stack, SU01.

[Former Member]

Hi,

While looking at the logs(std_server0.out), i found the following error.

Service com.sap.security.core.ume.service started. (3890 ms).

service security ================= ERROR =================

Core service security failed. J2EE Engine cannot be started.

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

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

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

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

Hope somebody can help me out.

Cheers,

Siva Maranani.