How To Fix ESH_ADM_MSG168 - Descriptions of connector "&1" are locked by user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ADM_MSG - ESH Administration and Monitoring Tool

• Message number: 168

• Message text: Descriptions of connector "&1" are 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_ADM_MSG168 - Descriptions of connector "&1" are locked by user &2 ?

  The SAP error message ESH_ADM_MSG168 indicates that the descriptions of a connector (identified by &1) are locked by a specific user (&2). This typically occurs in the context of the SAP Enterprise Search (SAP ESH) when a user is trying to modify or access the descriptions of a connector that is currently locked by another user.
  Cause:
  
  User Locking: The connector's descriptions are being edited or modified by another user, which prevents other users from making changes until the lock is released.
  Session Timeout: Sometimes, a user may have left a session open, causing the lock to persist even after they are no longer actively working on it.
  System Error: In some cases, a system error or crash may leave a lock in place that should have been released.
  
  Solution:
  
  Wait for Release: If the lock is held by another user, you may need to wait until that user completes their work and releases the lock.
  Identify the User: You can check which user is holding the lock. This can typically be done through transaction codes like SM12 (to view and manage locks) in the SAP GUI.
  Release the Lock: If you have the necessary authorizations, you can manually release the lock held by the user. In SM12, you can find the relevant lock entry and delete it. However, be cautious with this approach, as it may disrupt the work of the user who holds the lock.
  Contact the User: If possible, contact the user who is holding the lock to see if they can release it or if they are still actively working on the connector.
  Check for System Issues: If the lock seems to be persistent without an active user, check for any system issues or errors that may have caused the lock to remain in place.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 for lock management, SM21 for system logs, and ST22 for dumps, which can help diagnose issues.
  User Authorizations: Ensure that you have the necessary authorizations to manage locks and perform administrative tasks in the SAP system.
  Documentation: Refer to SAP documentation or support notes related to Enterprise Search and connector management for more detailed guidance and best practices.
  
  If the issue persists or if you are unsure about releasing locks, it may be advisable to consult with your SAP Basis team or support for further assistance.