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

SAP Error Message - Details

• Message type: E = Error

• Message class: ANST - ANST Message Class

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

  The SAP error message ANST035 indicates that a buffer trace is still active for a specific trace user. This typically occurs in the context of performance analysis or debugging within the SAP system, particularly when using the SAP Kernel's tracing tools.
  Cause:
  The error message is triggered when a buffer trace (a type of performance trace) has not been properly stopped or deactivated for a user. This can happen if:
  
  A trace was started for a user but not stopped correctly.
  The user session was terminated unexpectedly, leaving the trace active.
  There are multiple traces running for the same user, leading to conflicts.
  
  Solution:
  To resolve the ANST035 error, you can follow these steps:
  
  
  Stop the Active Trace:
  
  Use transaction code ST05 (SQL Trace) or ST12 (Combined Trace) to check if there are any active traces for the user.
  If you find an active trace, stop it by selecting the appropriate option to deactivate or stop the trace.
  
  
  
  Check for User Sessions:
  
  Ensure that there are no lingering user sessions that might still have the trace active. You can check this using transaction SM04 (User Overview) to see if the user is still logged in.
  
  
  
  Use Transaction ANST:
  
  If you are using the ABAP Trace (ANST), go to transaction ANST and check for any active traces. You can stop the trace from there as well.
  
  
  
  System Restart:
  
  If the above steps do not resolve the issue, consider restarting the application server. This can help clear any lingering traces that are not being released properly.
  
  
  
  Check for Authorization Issues:
  
  Ensure that the user has the necessary authorizations to start and stop traces. Lack of proper authorizations can sometimes lead to traces not being stopped correctly.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  ST05: SQL Trace
  ST12: Combined Trace
  ANST: ABAP Trace
  SM04: User Overview
  
  
  
  Documentation:
  
  Refer to SAP Help documentation for detailed information on tracing and performance analysis.
  Check SAP Notes for any known issues or patches related to tracing and performance tools.
  
  
  
  Performance Monitoring:
  
  Regularly monitor performance traces to ensure they are being managed properly and to avoid potential issues with system performance.
  
  
  
  By following these steps, you should be able to resolve the ANST035 error and manage traces effectively in your SAP environment.