How To Fix ESH_OM_OBJ_MODEL_RP2066 - Authorization check &1 has been locked by user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_OM_OBJ_MODEL_RP2 - Object Model Repository (2)

• Message number: 066

• Message text: Authorization check &1 has been locked by user &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_OM_OBJ_MODEL_RP2066 - Authorization check &1 has been locked by user &2 ?

  The SAP error message ESH_OM_OBJ_MODEL_RP2066 indicates that an authorization check for a specific object model has been locked by a user. This typically occurs in the context of the SAP Enterprise Search or the SAP NetWeaver platform, where certain objects or models may be locked for editing or processing by a user, preventing other users from accessing or modifying them.
  Cause:
  
  User Locking: The object model is currently being edited or processed by another user, which results in a lock being placed on it.
  Authorization Issues: The user attempting to access the object model may not have the necessary authorizations or permissions to perform the action.
  System Configuration: There may be configuration settings in the system that enforce locking mechanisms for certain operations.
  
  Solution:
  
  Identify the Locking User: Check which user has locked the object model. This can typically be done through transaction codes like SM12 (to view locks) or SM21 (to view system logs).
  Contact the Locking User: If possible, communicate with the user who has locked the object model to see if they can release the lock.
  Release the Lock: If the locking user is unavailable or the lock is no longer needed, an administrator can manually release the lock using transaction SM12.
  Check Authorizations: Ensure that the user attempting to access the object model has the necessary authorizations. This can be done by reviewing the user's roles and authorizations in transaction PFCG.
  Review System Configuration: If the locking behavior is unexpected, review the system configuration related to object models and authorization checks to ensure they are set up correctly.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks in the system.
  PFCG: To manage roles and authorizations.
  SU53: To analyze authorization failures.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to Enterprise Search and authorization management for further insights into managing object models and locks.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.