How To Fix /UI2/FCM058 - Catalog '&1' is locked by '&2'

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FCM -

• Message number: 058

• Message text: Catalog '&1' is locked by '&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 /UI2/FCM058 - Catalog '&1' is locked by '&2' ?

  The SAP error message /UI2/FCM058 Catalog '&1' is locked by '&2' indicates that a specific catalog in the SAP Fiori Launchpad is currently locked by another user or process. This can happen during various operations, such as editing or modifying the catalog, and it prevents other users from making changes until the lock is released.
  Cause:
  
  Concurrent Access: Another user is currently editing the catalog, which causes it to be locked.
  Session Timeout: A previous session may not have released the lock properly due to a timeout or an unexpected termination.
  System Error: There may be a system error or inconsistency that has caused the lock to persist.
  
  Solution:
  
  Wait and Retry: If another user is editing the catalog, you may need to wait until they finish their changes and release the lock.
  Identify the Locking User: Check who is currently locking the catalog (as indicated by &2 in the error message). You can communicate with that user to understand their actions.
  Release the Lock: If you have the necessary authorizations, you can manually release the lock:
  
  Use transaction code SM12 to view and delete the lock entries. Search for the relevant lock entry and delete it if appropriate.
  
  
  Check for Stale Locks: If you suspect that the lock is stale (e.g., due to a session that has ended unexpectedly), you can also check the system logs or use transaction SM21 to identify any issues.
  System Restart: In some cases, a system restart may be necessary to clear persistent locks, but this should be done with caution and typically requires coordination with your SAP Basis team.
  
  Related Information:
  
  Transaction Codes: 
  
  SM12: To view and manage lock entries.
  SM21: To check system logs for errors or issues.
  
  
  User Communication: If you are in a collaborative environment, communicate with your team members to coordinate changes to the catalog.
  Documentation: Refer to SAP Help documentation for more details on managing Fiori Launchpad catalogs and handling locks.
  
  If the issue persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.