How To Fix FOXX035 - No lock found: request &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FOXX -

• Message number: 035

• Message text: No lock found: request &1

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 FOXX035 - No lock found: request &1 ?

  The SAP error message FOXX035 "No lock found: request &1" typically occurs in the context of the SAP system's transport management system (TMS) or when dealing with transport requests. This error indicates that the system is unable to find a lock for the specified transport request, which can happen for several reasons.
  Causes:
  
  Transport Request Not Created Properly: The transport request may not have been created correctly or may have been deleted.
  Lock Table Issues: The lock table may not be updated correctly, leading to inconsistencies.
  System Configuration Issues: There may be configuration issues in the transport management system.
  User Authorization: The user may not have the necessary authorizations to access or modify the transport request.
  Transport Request Already Released: The transport request may have already been released, and the system is trying to access it in a way that requires a lock.
  
  Solutions:
  
  Check Transport Request Status: Verify the status of the transport request in transaction SE09 or SE10. Ensure that it exists and is in the correct state (e.g., modifiable).
  Recreate the Transport Request: If the transport request is missing or corrupted, consider recreating it.
  Check Lock Entries: Use transaction SM12 to check for any lock entries related to the transport request. If there are stale locks, they can be deleted.
  Review User Authorizations: Ensure that the user has the necessary authorizations to work with transport requests.
  System Restart: In some cases, a system restart may help clear any inconsistencies in the lock table.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches or updates.
  
  Related Information:
  
  Transaction Codes: 
  
  SE09/SE10: Transport Organizer
  SM12: Display and Delete Locks
  
  
  SAP Notes: Search the SAP Support Portal for notes related to transport issues or the specific error message FOXX035.
  Transport Management System (TMS): Familiarize yourself with TMS configuration and management, as understanding how transports work can help in troubleshooting.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.