How To Fix /STMC/CR_MSG373 - Error while using transport request; content build is locked

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_MSG -

• Message number: 373

• Message text: Error while using transport request; content build is locked

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 /STMC/CR_MSG373 - Error while using transport request; content build is locked ?

  The SAP error message /STMC/CR_MSG373 indicates that there is an issue with a transport request due to a locked content build. This typically occurs when the transport request is in a state that prevents changes or when the transport directory is locked for some reason.
  Cause:
  
  Locked Transport Request: The transport request may be locked because it is currently being processed or has been locked by another user or process.
  Incomplete Transport: The transport request may not have been completed properly, leading to a lock.
  Transport Directory Issues: There may be issues with the transport directory on the file system level, such as file locks or permissions.
  User Authorization: The user may not have the necessary authorizations to modify or release the transport request.
  
  Solution:
  
  
  Check Lock Status:
  
  Use transaction SE01 (Transport Organizer) to check the status of the transport request. Look for any locks and see if another user is currently working on it.
  You can also use transaction SM12 to check for any locks in the system. If you find a lock that should not be there, you can delete it (if you have the necessary authorizations).
  
  
  
  Release the Transport Request:
  
  If the transport request is locked due to being in a "modification" state, you may need to release it. This can be done in transaction SE01 or SE09.
  
  
  
  Check Transport Directory:
  
  Ensure that the transport directory is accessible and that there are no file system issues. Check for permissions and ensure that the transport directory is not locked at the OS level.
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to work with transport requests. This includes authorizations for creating, modifying, and releasing transport requests.
  
  
  
  Restart the Transport Process:
  
  If the issue persists, you may need to restart the transport process or the SAP system to clear any temporary locks.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error. SAP frequently updates their knowledge base with solutions for common issues.
  
  
  
  Related Information:
  
  Transport Management System (TMS): Understanding how TMS works can help in managing transport requests effectively.
  SAP Basis Administration: Knowledge of SAP Basis can be beneficial in troubleshooting transport-related issues.
  System Logs: Check system logs (transaction SM21) for any related errors that might provide more context on the issue.
  
  If the problem continues after trying the above solutions, it may be necessary to consult with your SAP Basis team or reach out to SAP support for further assistance.