Problem while creating user

[Former Member]

Hi

We have installed a SAP Netweaver 2004s system on AIX box.

We have installed the J2EE + ABAP Engine.

While creating the user from the portal we get the following error:

#1.5#1E656000400200710000008E000890AC00042D27C0FEBD4D#1175548671736#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase#sap.com/tc_wddispwda#com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.getPrivateIDPart()#J2EE_ADMIN#25759##punlparidm06.bmc_E60_602784150#J2EE_ADMIN#81b977c0e15f11dbc9551e6560004002#SAPEngine_Application_Thread[impl:3]_15##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector. Message: .##An exception was thrown in the UME/ABAP user management connector. Message: .

[EXCEPTION]

#2#Cannot create user QM?MVZ_{IMONY in ABAP backend system. Reason: The UME/ABAP adapter has recognized that the communication user is only assigned to the read-only role SAP_BC_JSF_COMMUNICATION_RO (or no role at all) in the backend system. Therefore UME was set to read-only mode for users from the backend system. See SAP Note 908911 for further information.#com.sap.security.core.persistence.datasource.PersistenceException: Cannot create user QM?MVZ}IMONY in ABAP backend system. Reason: The UME/ABAP adapter has recognized that the communication user is only assigned to the read-only role SAP_BC_JSF_COMMUNICATION_RO (or no role at all) in the backend system. Therefore UME was set to read-only mode for users from the backend system. See SAP Note 908911 for further information.

at com.sap.security.core.persistence.datasource.imp.R3Persistence.getPrivateIDPart(R3Persistence.java:2521)

at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.bindNewPrincipalDatabag(DataSourceBaseImplementation.java:340)

at com.sap.security.core.persistence.datasource.imp.R3Persistence$Transaction.bindNewPrincipalDatabag(R3Persistence.java:8727)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.bindNewPrincipalDatabag(PrincipalDatabagFactoryInstance.java:4640)

at com.sap.security.core.persistence.imp.PrincipalDatabag.getIDParts(PrincipalDatabag.java:1034)

What can be the problem here.

AM i missing any step.

Best Regards

Manoj

[Former Member]

For Other's reference.. even after the roles assignment the issue persists check the note below.

Note 1772222

Thanks and Regards,

Gopi

[christianojos_beltromagal]

Thanks Gopi !!! Problem solved.

[Former Member]

Hi Sumit,

the problem got solved

The following procedure needs to be adpated.

The protal user communicated with the SAPJSF(ABAP User) to talk top the ABAP Engine.

We had to add the role SAP_J2EE_GUEST and SAP_BC_BASIS_ADMIN to the

SAPJSF user.

Best Regards

Manoj

[Former Member]

Hi

Is the problem solved??

[Former Member]

Hi Manoj

Reason: The UME/ABAP adapter has recognized that the communication user is only assigned to the read-only role SAP_BC_JSF_COMMUNICATION_RO (or no role at all) in the backend system. Therefore UME was set to read-only mode for users from the backend system.

<b>Refer SAP Note 908911.</b>

You can check for the communication user that the role assigned to it is SAP_BC_JSF_COMMUNICATION_RO and this role does not give write permission it is read only role.

You can go to PFCG and check for the availability of SAP_BC_JSF_COMMUNICATION role which is having all the authorizations required for the communication user.

<b>Solution:</b>

If you want to enable write access from the UME to the ABAP backend system, assign the backend role SAP_BC_JSF_COMMUNICATION to the UME communication user (you do not need to remove other roles that are assigned to the user).

This will solve your problem.

Regards

Sumit Jain

**Reward points if useful