How To Fix SDRB100 - *** Messages for Log (Application Log) ***

SDRB100 - Overview

• Message type: E = Error

• Message class: SDRB - Document Relationship Browser

• Message number: 100

• Message text: *** Messages for Log (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 SDRB100 - *** Messages for Log (Application Log) *** ?

  The SAP error message SDRB100, which is related to the Application Log, typically indicates that there are issues with the logging mechanism in SAP. This message is often encountered when there are problems with the application log entries, such as when the log is full or when there are issues with the underlying data.
  
  Cause:
  
  Log Full: The application log may be full, which prevents new log entries from being created.
  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 the log from being written or accessed.
  
  Configuration Issues: There may be configuration problems in the logging settings or the application itself.
  
  
  Solution:
  
  
  Check Log Size: 
  
  Go to transaction SLG1 (Application Log) and check the size of the logs. If the log is full, you may need to delete old log entries or increase the log size.
  You can delete