How To Fix SRT_LOGGING035 - MSG = &1

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_LOGGING -

• Message number: 035

• Message text: MSG = &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 SRT_LOGGING035 - MSG = &1 ?

  The SAP error message SRT_LOGGING035 typically relates to issues with the logging of messages in the SAP system, particularly in the context of SAP Process Integration (PI) or SAP Process Orchestration (PO). The message usually indicates that there is a problem with the logging mechanism, which could be due to various reasons.
  Cause:
  
  Logging Configuration Issues: The logging configuration for the integration scenario may not be set up correctly.
  Database Issues: There may be issues with the database where the logs are stored, such as connectivity problems or insufficient space.
  Authorization Issues: The user or service account may not have the necessary authorizations to write logs.
  System Performance: High load on the system may lead to logging failures.
  Transport Issues: If the error occurs during a transport, it may be due to missing or incorrectly transported objects.
  
  Solution:
  
  Check Logging Configuration: Verify the logging settings in the SAP PI/PO configuration. Ensure that the logging level is set appropriately and that the logging destination is correctly configured.
  Database Health Check: Check the database for any issues. Ensure that there is enough space and that the database is running without errors.
  Authorization Check: Ensure that the user or service account has the necessary authorizations to write logs. You can check this in transaction SU53 or by reviewing the roles assigned to the user.
  Monitor System Performance: Use transaction ST03N or ST06 to monitor system performance. If the system is under heavy load, consider optimizing performance or scheduling jobs during off-peak hours.
  Review Transport Logs: If the error occurred after a transport, review the transport logs for any errors or warnings. Ensure that all necessary objects were transported correctly.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SLG1 (Application Log) to view logs related to the error.
  SAP Notes: Check for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  Documentation: Review the official SAP documentation for SAP PI/PO for best practices on logging and error handling.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.