Dispatcher is running but no server connected

[Former Member]

HI Experts

when i trying to open page using the url http://server:port i am getting the following error..

Dispatcher is running but no server connected.

I checked in default trace i got the following errors...

#Can not instantiate UserContext with given properties.

[EXCEPTION]

#1#com.sap.security.core.server.userstore.UserstoreException: Anonymous user configuration corrupt

Caused by: com.sap.security.api.UMException: Cannot find first configured anonymous user: J2EE_GUEST: USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!x

#Error#1#/System/Server#Java###Core service security failed. J2EE Engine cannot be

started.

#Error#1#/System/Server#Java###SNC properties not found ##

#1.5#00114326E0D9004300000001000018CB000446A52DD58C7A#1203575159360#com.sap.jms##com.sap.jms#######SAPEngine_System_Thread[impl:5]_6##0#0#Error##Java###A SecurityException was caught and the jms_provider continued with the attempt to retrieve user with Administrator right. The stacktrace of the suppressed exception is :

com.sap.security.core.server.userstore.UserstoreException: Could not get

group SAP_J2EE_ADMIN

SAPEngine_System_Thread[impl:5]_6##0#0#Error#1#/System/Server#Plain###The jms_provider service could not retrieve user with

Administrator right due to UME problems. No further operation with the jms_provider will be possible. See the trace file of the security service and the jms_provider service for more information and stacktrace#

Regards

Sowmya

[Former Member]

Hi check this Note 956867.

In note -->

Now the detailed steps for resolving the issue:

1) Use the configtool application (located at /usr/sap/<SID>/<instanceID>/j2ee/configtool/ directory).

In the tree, navigate to Global server configuration -> services -> com.sap.security.core.ume.service.

The list of UME properties appears.

- Select the ume.login.guest_user.uniqueids UME property in the list.

- In Value at the bottom of the screen, enter the new (temporary) value - some known user that surely exists in the engine - for example you could even set the Administrator's userID.

- Choose Set.

- Choose (Apply changes), for saving.

2) Restart the J2EE engine so the changes to take effect.

Now the engine should start successfully.

3) Use the Visual Administrator (located at /usr/sap/<SID>/<instanceID>/j2ee/admin/ directory), go to Server -> services -> Security Provider -> Runtime tab -> User Management tab.

- Switch to "edit" mode (the pencil-like button).

- Click on the "Create User" button and enter Guest in the "user name" field. Set some password and click on the OK button.

- Do search for that user and you will get it in the list. Select it and its properties will appear on the right hand side.

Find the "No password change required" check box and select it.

Close the Visual Administrator.

4) Now start the configtool again and restore the Guest user account in the ume.login.guest_user.uniqueids UME property.

This step is similar to step #1). However this time you should set Guest as a value for the ume.login.guest_user.uniqueids property.

5) Finally close the configtool and restart the J2EE engine.

Now the J2EE engine should start and work properly.

Hope it's help.

Regards,award if helpful.

Edited by: Sergo Beradze on Feb 26, 2008 9:21 AM

[Former Member]

Hi Sowmya,

The user j2ee_guest might not have the authorization or check the password for that user,

You can use j2ee_admin user for looking the system components and also for user management.

Also check the user j2ee_guest exsists or not in the client 001.

Reward points if helpfull.

Regards,

Vamshi.

[Former Member]

1. Please start the configtool

cluster-data->

->Global server configuration->

->com.sap.security.core.ume.service.

In here you will see many UME parameters. I would like you to scroll

down to the section ume.r3.connection.master.

In this section, please verify that the following are set:

ume.r3.connection.master.ashost (R/3 application server host)

ume.r3.connection.master.client

ume.r3.connection.master.passwd

ume.r3.connection.master.sysnr

ume.r3.connection.master.user (should be 'SAPJSF')

These parameters are used by J2EE to communicate with the R/3 system

for User Management functions and should be valid connection

parameters for the integrated R/3 system.

2.- Please go to transaction SU01 in the client (ume.r3.connection.master.client) and check the

SAPJSF ,J2EE_ADMIN and J2EE_GUEST users.

Please verify that the users is not locked. If it's

locked, please unlock the user and verify that the password in R/3 is

matching the one set for ume.r3.connection.master.passwd parameter.