How To Fix RSTT0035 - Trace not found

SAP Error Message - Details

• Message type: E = Error

• Message class: RSTT0 - Trace Tool: Message Class Engine Layer

• Message number: 035

• Message text: Trace not found

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 RSTT0035 - Trace not found ?

  The SAP error message RSTT0035, which states "Trace not found," typically occurs when you are trying to access a trace that does not exist or has been deleted. This can happen for various reasons, such as the trace file being removed, the trace not being generated due to an error in the tracing process, or the trace being for a session that has already ended.
  Causes:
  
  Trace File Deletion: The trace file may have been deleted manually or by a system cleanup process.
  Trace Not Started: The trace may not have been started for the session or transaction you are trying to analyze.
  Session Ended: The session for which you are trying to retrieve the trace may have already ended, and the trace is no longer available.
  Incorrect Trace ID: You may be using an incorrect or outdated trace ID to look for the trace.
  
  Solutions:
  
  Verify Trace ID: Ensure that you are using the correct trace ID. Double-check the ID you are trying to access.
  Check Trace Status: Use transaction code ST01 (System Trace) or ST05 (SQL Trace) to check if the trace was started and is currently active.
  Re-run the Trace: If the trace was not started, you may need to re-run the transaction or process while ensuring that the trace is enabled.
  Check for Cleanup Jobs: Investigate if there are any background jobs or system settings that might be deleting trace files automatically.
  Consult Logs: Check the system logs (transaction SM21) for any errors or messages related to tracing that might provide additional context.
  Use Alternative Tools: If the trace is not available, consider using other performance analysis tools or methods, such as transaction ST12 (Combined Trace) or transaction SAT (ABAP Trace).
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes like ST01, ST05, ST12, and SAT for tracing and performance analysis.
  SAP Notes: Check SAP Notes for any known issues or updates related to tracing and error messages.
  Documentation: Review SAP documentation on tracing and performance analysis for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP Basis team or SAP support for further assistance.