Unable to unlock admin user

[Former Member]

Hello,

we've had some problems with the Administrator account due to the fact that it was locked by the Administrator. After using the emergency sap* user to login to the Visual Administrator we couldn't unlock the administrator account.

The following error was displayed:

Unable to unlock user!

com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is:

java.lang.ClassNotFoundException: com.sap.security.core.persistence.datasource.PersistenceException at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:670) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:648) at com.sap.engine.services.rmi_p4.Call.getResultStream(Call.java:200) at com.sap.engine.services.security.remote.RemoteUserStoreInfo_Stub.writeUserProperty(RemoteUserStoreInfo_Stub.java:453) at com.sap.engine.services.security.gui.userstore.usermanagement.UserPropertiesPanel.lockAction(UserPropertiesPanel.java:532) at com.sap.engine.services.security.gui.userstore.usermanagement.UserPropertiesPanel.actionPerformed(UserPropertiesPanel.java:310)

at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)

...

Caused by: java.lang.ClassNotFoundException: com.sap.security.core.persistence.datasource.PersistenceException

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

...

Has anyone else seen this error?

Kind regards,

Edwin Oldenburg

[Former Member]

Hi Edwin,

Haven't seen the error, but you can log on to the UME administration console using the SAP* user and fix the problem:

http://<J2EE_Engine_Server>:<J2EE_Engine_HTTP_port>/useradmin

http://myserver.mycompany.com:50200/useradmin

Good luck,

Imko

[Former Member]

Hi Imko,

thanks for the info. But strangely the login with SAP* didn't work and I was automatically send back to the login page.

In the meantime I've found the answer. The user was also locked in the ABAP stack, only I looked in the wrong client when I checked this for the first time.

After unlocking this user in the ABAP stack (correct client this time) everything worked fine again.

Thanks and Goodbye

Edwin