How To Fix RDSV_DS_GEN_XX154 - No access to PSE-file for application in system &1 on server &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RDSV_DS_GEN_XX - Regulatory validation of certificates

• Message number: 154

• Message text: No access to PSE-file for application in system &1 on server &2

What causes this issue?

The system runs a cloud service that requests an SSF-application to sign
a document with a digital signature.
The SSF-application is inconsistently configured to generate this
signature in this system.

System Response

The SSF-application requires a system with a specific configured
certified PSE-file and is legally not allowed to generate a digital
signature without it.

How to fix this error?

The Secure Storage and Forward (SSF) environment of the dedicated cloud
system must be correctly setup. This setup change must be completed by
the provider of the cloud service you use.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RDSV_DS_GEN_XX154 - No access to PSE-file for application in system &1 on server &2 ?

  The SAP error message RDSV_DS_GEN_XX154 indicates that there is no access to the PSE (Personal Security Environment) file for a specific application in the given system and server. This error typically arises in the context of security and encryption, where the PSE file is crucial for managing certificates and keys.
  Cause:
  
  File Permissions: The user or process trying to access the PSE file may not have the necessary permissions to read or write to the file.
  File Location: The PSE file may not be located in the expected directory, or the path to the PSE file may be incorrect.
  File Corruption: The PSE file itself may be corrupted or improperly configured.
  Configuration Issues: There may be issues with the configuration of the application or the SAP system that prevent access to the PSE file.
  Missing PSE: The PSE file may not exist at all, which can happen if it was never created or was deleted.
  
  Solution:
  
  
  Check Permissions: Ensure that the user or service account running the SAP application has the necessary permissions to access the PSE file. You may need to adjust the file permissions or ownership.
  
  
  Verify File Path: Check the configuration settings to ensure that the path to the PSE file is correct. You can find the PSE file typically in the directory specified in the SAP profile parameters (e.g., DIR_PSE).
  
  
  Recreate PSE: If the PSE file is missing or corrupted, you may need to recreate it. This can be done using transaction STRUST in the SAP GUI, where you can manage the PSE files.
  
  
  Check Configuration: Review the configuration of the application and the SAP system to ensure that everything is set up correctly. This includes checking any relevant profiles and parameters.
  
  
  Consult Logs: Look at the SAP system logs (transaction SM21) and the application logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  
  
  Restart Services: Sometimes, simply restarting the relevant SAP services or the entire system can resolve transient issues related to file access.
  
  
  Related Information:
  
  PSE Management: The PSE files are managed through the SAP Trust Manager (transaction STRUST), where you can view, create, and manage PSE files and certificates.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to the official SAP documentation for more details on PSE files, security configurations, and troubleshooting steps.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.