How To Fix /TMF/TOM035 - System canÆt create the log file.

SAP Error Message - Details

• Message type: E = Error

• Message class: /TMF/TOM -

• Message number: 035

• Message text: System canÆt create the log file.

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 /TMF/TOM035 - System canÆt create the log file. ?

  The SAP error message /TMF/TOM035 System can’t create the log file typically indicates that the system is unable to create or write to a log file due to various reasons. Here are some common causes, potential solutions, and related information:
  Causes:
  
  File System Permissions: The user under which the SAP application server is running may not have the necessary permissions to create or write to the log file directory.
  Disk Space Issues: The disk where the log files are supposed to be created may be full, preventing any new files from being created.
  Directory Path Issues: The specified directory for the log files may not exist or may be incorrectly configured in the system settings.
  File System Quotas: There may be quotas set on the file system that limit the amount of disk space or number of files that can be created by the user.
  SAP Configuration Issues: There may be misconfigurations in the SAP system that affect logging.
  
  Solutions:
  
  
  Check Permissions:
  
  Verify that the user running the SAP instance has the necessary permissions to write to the log file directory. You can check and modify permissions using commands like chmod and chown in Unix/Linux systems.
  
  
  
  Check Disk Space:
  
  Use commands like df -h (Unix/Linux) or check the disk properties in Windows to ensure there is sufficient disk space available. If the disk is full, consider cleaning up unnecessary files or increasing disk capacity.
  
  
  
  Verify Directory Path:
  
  Check the configuration settings in the SAP system (e.g., using transaction codes like RZ10 for profile parameters) to ensure that the log file directory is correctly specified and exists.
  
  
  
  Check File System Quotas:
  
  If file system quotas are in place, check the limits for the user and adjust them if necessary.
  
  
  
  Review SAP Configuration:
  
  Ensure that the logging configuration in the SAP system is set up correctly. This may involve checking the relevant parameters in the instance profile or using transaction codes like RZ11.
  
  
  
  Restart the SAP Instance:
  
  Sometimes, simply restarting the SAP instance can resolve temporary issues related to file creation.
  
  
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  System Logs: Review the system logs (using transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  SAP Community: Consider searching or posting in the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or consult SAP support for further assistance.