How To Fix 0S064 - RFC trace is not switched on

SAP Error Message - Details

• Message type: E = Error

• Message class: 0S - Messages for the SQL trace

• Message number: 064

• Message text: RFC trace is not switched on

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 0S064 - RFC trace is not switched on ?

  The SAP error message 0S064 RFC trace is not switched on typically indicates that the Remote Function Call (RFC) tracing is not enabled for the system or the specific user session. This can occur when you are trying to analyze performance issues or troubleshoot problems related to RFC calls, but the tracing feature is not activated.
  Cause:
  
  Tracing Not Enabled: The most common cause is that the RFC tracing has not been enabled in the system settings.
  User Authorization: The user may not have the necessary authorizations to enable RFC tracing.
  System Configuration: The system may not be configured to allow RFC tracing for certain types of calls or users.
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Enable RFC Tracing:
  
  Go to transaction SM59 (RFC Destinations).
  Select the relevant RFC destination.
  Click on the Technical Settings tab.
  Ensure that the Trace option is enabled. If not, enable it.
  
  
  
  Use Transaction ST01:
  
  Go to transaction ST01 (System Trace).
  Activate the trace for RFC by selecting the appropriate options.
  After enabling, reproduce the issue to capture the trace.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to enable and view RFC traces. This may require checking roles and profiles assigned to the user.
  
  
  
  Check System Configuration:
  
  Consult with your SAP Basis team to ensure that the system is configured correctly to allow RFC tracing.
  
  
  
  Use Transaction ST05:
  
  You can also use transaction ST05 (SQL Trace) to trace database calls if you suspect that the issue is related to database performance.
  
  
  
  Related Information:
  
  RFC Tracing: This is a diagnostic tool in SAP that helps in monitoring and analyzing the performance of RFC calls. It can provide insights into the time taken for calls, errors, and other performance metrics.
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or fixes related to RFC tracing.
  Documentation: Refer to SAP Help documentation for more details on enabling and using RFC tracing effectively.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.