How To Fix 1S406 - PSE does not exist in database

SAP Error Message - Details

• Message type: E = Error

• Message class: 1S - Messages for SSF ("Secure Store & Forward")

• Message number: 406

• Message text: PSE does not exist in database

What causes this issue?

The cryptographic keys and certificates required for the application
are stored in a PSE. However, the PSE does not exist in the database.

System Response

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

How to fix this error?

Create the PSE in the <DS:TRAN.STRUST>Trust-Manager</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1S406 - PSE does not exist in database ?

  The SAP error message "1S406 PSE does not exist in database" typically indicates that the system is unable to find a Personal Security Environment (PSE) that is required for secure communication, such as SSL or secure network connections. PSEs are used to store cryptographic keys and certificates.
  Cause:
  
  Missing PSE: The PSE file may not have been created or may have been deleted.
  Incorrect Configuration: The system may not be configured correctly to point to the existing PSE.
  Database Issues: There may be issues with the database that prevent the PSE from being accessed.
  Transport Issues: If the PSE was transported from another system, it may not have been imported correctly.
  
  Solution:
  
  
  Create a New PSE:
  
  You can create a new PSE using the transaction code STRUST in the SAP GUI.
  Navigate to the appropriate PSE (e.g., SSL Client PSE, SSL Server PSE) and create a new one if it does not exist.
  
  
  
  Check Existing PSE:
  
  Use transaction STRUST to check if the PSE exists and is correctly configured.
  If it exists, ensure that it is properly maintained and that the necessary certificates are in place.
  
  
  
  Import PSE:
  
  If you have a backup of the PSE, you can import it back into the system using the STRUST transaction.
  
  
  
  Check Authorization:
  
  Ensure that the user has the necessary authorizations to access and manage PSEs.
  
  
  
  Database Consistency:
  
  Check the database for any inconsistencies or issues that may be affecting the PSE.
  
  
  
  Transport Management:
  
  If the PSE was transported, ensure that the transport was successful and that all necessary objects were included.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  STRUST: Manage PSEs and certificates.
  STRUSTSSO2: For Single Sign-On configurations.
  
  
  
  Documentation: Refer to SAP Help documentation for detailed steps on managing PSEs and SSL configurations.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to PSEs and the error message.
  
  
  System Logs: Review system logs for additional error messages or warnings that may provide more context about the issue.
  
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.