cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE_GUEST user locked in PX7

Former Member
0 Kudos

Hi SDNers,

Our Scenario is Idoc-->SOAP Adapter.

The files were picked up from the sender side and delivered successfully to the receiver side. But we are getting errors in Acknowledgement.

When looked into the trace files, we found that the error was due to J2EE_GUEST user locked. This is the user that is being used at the receiver end.

SECURITY LOG

1.5#00112508C2A8006D0000279B000F309A0004622CF5320E36#1233845138624#/System/Security/Usermanagement##com.sap.security.core.persistence#J2EE_GUEST#0####a770ea00f39311dda9e400112508c2a8#SAPEngine_Application_Thread[impl:3]_23##0#0#Warning#1#com.sap.security.core.persistence#Java#Search in the backend resulted in an exception. The search result returned to the application might be incomplete. Reason: .##Search in the backend resulted in an exception. The search result returned to the application might be incomplete. Reason: .#1#User is locked. Please notify the person responsible#

But we have not locked the user manually.

How the user got locked?

Is there any other possibilities to lock an user other than using SU01?

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi All,

Thnx for your inputs.But the user is unlocked already.Could anyone please tell me where to get the details as in who has locked it and when?

We have tried searching the same in SU01,SM04,SUIM,STAD and didn't get any info...

Would appriciate your valuable inputs on this

Thnx in advance...

Former Member
0 Kudos

Hi,

Try Unlocking the User using a super user Roles Like User==DDIC and the associated passwork from the basis guy.

BR,

sainath

JoelTrinidade
Active Contributor
0 Kudos

Hi Anguraj,

The only reason for a user to get locked is because of incorrect logon unless the user has been explicitly locked by adminstrators.

j2ee_guest is used for anonymous access to the AS Java. By default, this user is locked.

Rgds

joel