How To Fix RSEC664 - There are new entries in the log

RSEC664 - Overview

• Message type: E = Error

• Message class: RSEC -

• Message number: 664

• Message text: There are new entries in the 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 RSEC664 - There are new entries in the log ?

  The SAP error message RSEC664, which states "There are new entries in the log," typically relates to issues in the context of SAP's security and authorization management, particularly in the area of Business Intelligence (BI) or SAP BW (Business Warehouse). This message indicates that there are new entries in the authorization log that need to be reviewed.
  
  Cause:
  
  Authorization Changes: The error may occur when there are recent changes to user authorizations or roles that have not been reviewed or processed.
  Log Entries: New entries in the authorization log indicate that there are actions or transactions that have been executed by users that require attention, possibly due to failed authorizations or security checks.
  System Configuration: It may also arise from system configuration settings that require monitoring of authorization logs.
  
  
  Solution:
  
  
  Review the Authorization Log:
  
  Go to transaction code SUIM (User Information System) or SU53 (Display Authorization Check) to review the authorization logs.
  Check for any failed authorization checks