cancel
Showing results for 
Search instead for 
Did you mean: 

errors solman_setup initial configuration in StartSLD Configuration step

Former Member
0 Kudos
187

Getting an authentication error when trying to sign into SAP netWeaver using the solman_admin account created in the first step of the initial configuration. I tried going back and creating another user and setting a new password but am still getting the same User authentication failed. I am able to sign in as the J2EE_ADMIN user id here and continue the configuration but get errors on step 66 of 137 Maintain SLD data supplier user. Error: Name or password is incorrect. I am able to click on in the error box the Step: Maintain SLD data supplier user which takes me into the J2EE Engine Useradministration. In here I do not see the solman_admin userid if I try to create it I get the error Current suer has user creation permissions in the UME, but cannot create users in the back-end system (data source). The original and possibly untranslated message was: "No active writeable datasource found for the user creation, check your Persistence Configuration."

I do find my SLD data supplier user SLDDSUSER but am not sure what to fix here for step 66 noted above.

Within Abap I am able to sign in as solman_admin successfully

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

The answer provided by Garduño Azael, above is correct. I'm just completing the solution by adding the steps to change your UME destination to client 100 in this scenario, in case someone else runs into this issue:

1) Go to: http://solman_hostname:solman_port/useradmin

2) Logon as J2ee_admin

3) Click on Configuration on the top of the UserAdmin screen

4) Click on the Abap System tab

5) Click on Modify button, and change the UME source to client 100

6) Save

Jose

Former Member
0 Kudos

Hello,

Review the UME configuration in J2EE. After a fresh install of solman UME data source of J2EE is set to the ABAP stack, client 001.

Usually you perform the ABAP configuration before running solman_setup. In the ABAP configuration you set your working client, for example 100, then you log in to your client, 100 in this example, and run solman_setup. First task in initial configuration is to create the user SOLMAN_ADMIN, which gets created in the client you ran SOLMAN_SETUP, but UME still points to 001, then J2ee configuration in solman setup is looking for user SOLMAN_ADMIN in client 001.

please set the client in UME configuration datasource to your working client.

regards

Former Member
0 Kudos

hi

check this [Prepare the AS ABAP System as UME Data Source |http://help.sap.com/erp2005_ehp_04/helpdata/en/42/e4f0dfe4cc3ee1e10000000a1553f6/frameset.htm]

Jansi

Former Member
0 Kudos

Change the permission of the user SAPJSF to SAP_BC_JSF_COMMUNICATION from SAP_BC_JSF_COMMUNICATION_RO which is giving the writing access issue.

SAPJSF user acts as the bridging user between ABAP and JAVA stack. So it needs the write access to perform any java related activities.

Do not forget to generate the role SAP_BC_JSF_COMMUNICATION and user comparision.

Thanks,

Lijin Xavier

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

What is the UME of your portal system ?

Create user in UME and assign portal roles in UME only like SAP_J2ee_Admin etc. then you will be able to login into the portal.

Thanks

Sunny

Former Member
0 Kudos

As I said in my initial problem I cannot create the solman_admin in the UME. I access the UME via "http://cvlnxsp1.corp.cvpsnet.net:51000/webdynpro/dispatcher/sap.com/tcsecumewdumeadmin/UmeAdminApp" (J2EE Engine Useradministration)

What role or group do I need to give the J2ee_admin id to allow me to get around the error when clicking on create user in the UME

Current user has user creation permissions in the UME, but cannot create users in the back-end system (data source). The original and possibly untranslated message was: "No active writeable datasource found for user creation, check your Persistence Configuration.".

In ABAP I have given the j2ee_admin sap_all so I am assuming there is a role or group that j2ee_admin has to have in the UME?