How To Fix SMI_GENERAL067 - Message cannot be added in application log

SAP Error Message - Details

• Message type: E = Error

• Message class: SMI_GENERAL -

• Message number: 067

• Message text: Message cannot be added in application log

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 SMI_GENERAL067 - Message cannot be added in application log ?

  The SAP error message SMI_GENERAL067 indicates that a message cannot be added to the application log. This error typically arises in the context of the SAP Application Log (transaction SLG1), which is used to log messages related to various processes in SAP.
  Causes:
  
  Log Size Limit: The application log may have reached its maximum size limit, preventing new entries from being added.
  Authorization Issues: The user may not have the necessary authorizations to write to the application log.
  Database Issues: There may be issues with the database that prevent writing new entries.
  Configuration Issues: The application log may not be properly configured, or there may be inconsistencies in the log settings.
  System Performance: High system load or performance issues may temporarily prevent logging.
  
  Solutions:
  
  
  Check Log Size:
  
  Use transaction SLG2 to check the size of the application log. If it is full, you may need to delete old logs or archive them to free up space.
  You can also adjust the log size settings in the configuration if necessary.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to write to the application log. Check the roles and profiles assigned to the user.
  
  
  
  Database Check:
  
  Check the database for any issues. You may need to consult with your database administrator to ensure that the database is functioning correctly and that there are no locks or performance issues.
  
  
  
  Configuration Review:
  
  Review the configuration settings for the application log. Ensure that the log is set up correctly and that there are no inconsistencies.
  
  
  
  System Performance:
  
  Monitor system performance and check for any bottlenecks. If the system is under heavy load, consider optimizing performance or scheduling logging during off-peak hours.
  
  
  
  SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that may resolve known issues.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SLG1: Display Application Log
  SLG2: Manage Application Log
  SLG3: Delete Application Log
  
  
  
  SAP Documentation: Refer to the official SAP documentation for more details on application logging and troubleshooting.
  
  
  Support: If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.
  
  
  By following these steps, you should be able to identify the cause of the SMI_GENERAL067 error and implement a solution to resolve it.