How To Fix STRUSTCR015 - Selected CRL is not saved (&1)

SAP Error Message - Details

• Message type: E = Error

• Message class: STRUSTCR - Certificate Revocation Configuration

• Message number: 015

• Message text: Selected CRL is not saved (&1)

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 STRUSTCR015 - Selected CRL is not saved (&1) ?

  The SAP error message STRUSTCR015, which states "Selected CRL is not saved (&1)," typically occurs in the context of managing Certificate Revocation Lists (CRLs) within the SAP Trust Manager (transaction STRUST). This error indicates that the selected CRL has not been saved properly, which can prevent the system from validating certificates against the revocation list.
  Cause:
  
  CRL Not Saved: The most common cause is that the CRL was not saved after being imported or modified. This can happen if the user did not complete the save operation.
  Insufficient Authorizations: The user may not have the necessary authorizations to save changes in the Trust Manager.
  Technical Issues: There may be underlying technical issues, such as database problems or system configuration errors, that prevent the CRL from being saved.
  Invalid CRL Format: The CRL file being imported may be in an incorrect format or corrupted.
  
  Solution:
  
  Save the CRL: Ensure that after importing or modifying the CRL, you click the "Save" button in the Trust Manager to save the changes.
  Check Authorizations: Verify that the user has the necessary authorizations to perform actions in the Trust Manager. This may require checking roles and permissions in the SAP system.
  Re-import the CRL: If the CRL was not saved due to an error, try re-importing it and ensure that you save it afterward.
  Check CRL Format: Ensure that the CRL file is in the correct format and is not corrupted. You can validate the CRL using external tools or by checking its properties.
  Review System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Consult SAP Notes: Look for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction STRUST: This is the transaction code used to access the Trust Manager in SAP, where you can manage certificates and CRLs.
  CRL (Certificate Revocation List): A CRL is a list of certificates that have been revoked by the certificate authority (CA) before their scheduled expiration date.
  SAP Security: Understanding the broader context of SAP security and how certificates and CRLs are used for secure communications can help in troubleshooting related issues.
  
  If the problem persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.