How To Fix E2E_TESTING035 - OFF: Buffer trace is still active for trace user &1

SAP Error Message - Details

• Message type: E = Error

• Message class: E2E_TESTING - Messages for E2E Testing Agent

• Message number: 035

• Message text: OFF: Buffer trace is still active for trace user &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 E2E_TESTING035 - OFF: Buffer trace is still active for trace user &1 ?

  The SAP error message E2E_TESTING035 indicates that a buffer trace is still active for a specific trace user. This typically occurs in the context of performance analysis or debugging, where a buffer trace is used to monitor database operations and performance metrics.
  Cause:
  The error message is triggered when:
  
  A buffer trace was started for a user (the trace user indicated by &1 in the message) and has not been stopped.
  The system is trying to perform an operation that requires the buffer trace to be inactive.
  
  Solution:
  To resolve this issue, you need to stop the buffer trace for the specified user. Here are the steps to do this:
  
  
  Identify the Trace User: Check the user indicated in the error message (&1).
  
  
  Stop the Buffer Trace:
  
  Use transaction code ST05 (SQL Trace) or ST12 (Single Transaction Analysis) in the SAP GUI.
  In ST05, you can find the option to deactivate the trace. Make sure to select the correct user and stop the trace.
  If you are using ST12, you can also stop the trace from the analysis screen.
  
  
  
  Verify: After stopping the trace, you can verify that it has been deactivated by checking the trace status for the user.
  
  
  Retry the Operation: Once the trace is stopped, retry the operation that triggered the error message.
  
  
  Related Information:
  
  Buffer Trace: This is a performance monitoring tool in SAP that helps in analyzing the database operations and can be useful for debugging performance issues.
  Transaction Codes:
  
  ST05: SQL Trace - Used to trace SQL statements executed by the application.
  ST12: Single Transaction Analysis - Combines SQL trace and runtime analysis for a more comprehensive view.
  
  
  User Authorization: Ensure that you have the necessary authorizations to start and stop traces for users in the system.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis team or refer to SAP Notes for further troubleshooting.