How To Fix STRUSTCR029 - No changes need to be saved

STRUSTCR029 - Overview

• Message type: E = Error

• Message class: STRUSTCR - Certificate Revocation Configuration

• Message number: 029

• Message text: No changes need to be saved

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 STRUSTCR029 - No changes need to be saved ?

  The SAP error message STRUSTCR029 ("No changes need to be saved") typically occurs in the context of the SAP Trust Manager (transaction STRUST) when you attempt to save changes to a trust relationship or SSL configuration, but there are no actual changes to save. This can happen for a few reasons:
  
  Cause:
  
  No Modifications Made: You may have opened the Trust Manager and navigated through the settings without making any changes. The system detects that the current configuration is the same as the saved configuration.
  Uncommitted Changes: If you made changes but did not commit them properly, the system may not recognize any changes to save.
  System Behavior: Sometimes, the system may behave this way due to caching or session issues, where it does not recognize the changes made in the current session.
  
  
  Solution:
  
  Verify Changes: Ensure that you have actually made changes to the configuration. Check if you have modified any entries, such as adding