How To Fix /SMB/TRANSP_INFRA034 - No application log to be saved

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/TRANSP_INFRA -

• Message number: 034

• Message text: No application log to be saved

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 /SMB/TRANSP_INFRA034 - No application log to be saved ?

  The SAP error message /SMB/TRANSP_INFRA034 No application log to be saved typically indicates that there is an issue with the application log functionality in the SAP system. This error can occur in various scenarios, often related to transport requests or application logging processes.
  Cause:
  
  No Logs Available: The most straightforward cause is that there are no application logs available to be saved. This can happen if the process that was supposed to generate logs did not execute properly or if the logs were already deleted.
  Authorization Issues: The user may not have the necessary authorizations to access or save the application logs.
  Configuration Issues: There may be configuration issues in the logging framework or the transport system that prevent logs from being generated or saved.
  System Errors: There could be underlying system errors or inconsistencies that are preventing the application log from being created or accessed.
  
  Solution:
  
  Check Log Generation: Ensure that the process that is supposed to generate the application log is functioning correctly. You may need to review the relevant transaction or program to see if it is executing as expected.
  Review Authorizations: Verify that the user has the necessary authorizations to access and save application logs. You can check this in transaction SU53 or by reviewing the user's roles and authorizations.
  Check Configuration: Review the configuration settings related to application logging. This can include checking the settings in transaction SLG0 (Application Log: Maintain Object) to ensure that the logging object is correctly configured.
  System Logs: Check the system logs (transaction SM21) for any related errors or warnings that might provide more context about the issue.
  Transport Request: If this error occurs during a transport request, ensure that the transport request is correctly configured and that all necessary objects are included.
  Re-run the Process: If applicable, try re-running the process that was supposed to generate the logs to see if the issue persists.
  
  Related Information:
  
  Transaction Codes:
  
  SLG1: Display Application Log
  SLG0: Maintain Application Log Objects
  SM21: System Log
  SU53: Authorization Check
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review SAP documentation on application logging and transport management for more detailed information on how these systems work.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.