How To Fix FPP800 - Cannot add message to log; contact SAP

SAP Error Message - Details

• Message type: E = Error

• Message class: FPP - FPP: Message Class

• Message number: 800

• Message text: Cannot add message to log; contact SAP

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 FPP800 - Cannot add message to log; contact SAP ?

  The SAP error message FPP800, which states "Cannot add message to log; contact SAP," typically indicates an issue with the logging mechanism in the SAP system. This error can arise due to various reasons, including:
  Causes:
  
  Log Table Issues: The log table where messages are stored may be full or corrupted.
  Authorization Issues: The user may not have the necessary authorizations to write to the log.
  Database Issues: There could be underlying database problems, such as connectivity issues or database corruption.
  System Configuration: Incorrect configuration settings in the SAP system could prevent logging.
  Transport Issues: If the error occurs during a transport, it may be related to transport logs.
  
  Solutions:
  
  
  Check Log Tables: 
  
  Use transaction codes like SE11 or SE16 to check the relevant log tables (e.g., FPP_LOG or similar) for any issues. If the table is full, consider archiving old logs or increasing the table size.
  
  
  
  Review Authorizations: 
  
  Ensure that the user has the necessary authorizations to write to the log. This can be checked in transaction SU53 or by reviewing the user's roles and authorizations.
  
  
  
  Database Health Check: 
  
  Perform a health check on the database to ensure it is functioning correctly. This may involve checking for locks, running consistency checks, or consulting with your database administrator.
  
  
  
  System Configuration Review: 
  
  Review the configuration settings related to logging in the SAP system. This may involve checking parameters in transaction RZ10 or RZ11.
  
  
  
  Check for Transport Issues: 
  
  If the error occurs during a transport, check the transport logs for any errors or issues that may have occurred during the transport process.
  
  
  
  Contact SAP Support: 
  
  If the issue persists after trying the above solutions, it may be necessary to contact SAP support for further assistance. Provide them with detailed information about the error, including any relevant logs or screenshots.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE16 (Data Browser), SU53 (Authorization Check), and RZ10/RZ11 (Profile Parameters).
  SAP Notes: Search for SAP Notes related to the FPP800 error message in the SAP Support Portal. There may be specific notes addressing known issues or providing patches.
  System Logs: Check system logs (transaction SM21) for any related errors or warnings that could provide additional context for the issue.
  
  By following these steps, you should be able to diagnose and potentially resolve the FPP800 error in your SAP system.