00146 - Error in configuration of SAP logon tickets

SAP Error Message - Details

• Message type: E = Error

• Message class: 00 -

• Message number: 146

• Message text: Error in configuration of SAP logon tickets

What causes this issue?

The system was not configured for SAP logon tickets:
At least one of the two parameters login/create_sso2_ticket and
login/accept_sso2_ticket currently has the value 0.

System Response

It is not possible to use SAP logon tickets.
Therefore, there is also no single sign-on support when using SAPGUI
HTML Control and calling local ICF services (see SAP note 612670).

How to fix this error?

Contact the system administrator.

Procedure for System Administrators

<DS:TRAN.RZ11>Check the values of the two profile parameters</> and set
them to suitable values, for example:
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
After setting the profile parameters (using <DS:TRAN.RZ10>transaction
RZ10</>) you must restart the application server for the new values to
become active.

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 00146 - Error in configuration of SAP logon tickets ?

  The SAP error message "00146 Error in configuration of SAP logon tickets" typically indicates an issue with the configuration of SAP logon tickets, which are used for single sign-on (SSO) in SAP systems. This error can arise due to various reasons, including incorrect settings in the SAP system or issues with the underlying infrastructure.
  Causes:
  
  Incorrect Configuration: The configuration settings for logon tickets in the SAP system may not be set up correctly. This includes settings in the profile parameters or in the SAP Web Dispatcher.
  Missing or Incorrect SSL Configuration: If SSL is not configured properly, it can lead to issues with secure communication, which is necessary for logon tickets.
  Expired or Invalid Certificates: If the certificates used for secure communication are expired or invalid, it can cause authentication issues.
  User Authorization Issues: The user may not have the necessary authorizations to use logon tickets.
  Network Issues: Problems with the network or firewall settings can prevent proper communication between the client and the SAP server.
  
  Solutions:
  
  
  Check Configuration Settings:
  
  Verify the settings in the SAP system for logon tickets. This includes checking the profile parameters such as login/ticket and login/create_sso2_ticket.
  Ensure that the SAP Web Dispatcher is configured correctly if it is being used.
  
  
  
  SSL Configuration:
  
  Ensure that SSL is properly configured in the SAP system. Check the SSL certificates and make sure they are valid and not expired.
  Use transaction code STRUST to manage and check the SSL certificates.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to use logon tickets. This may involve checking roles and profiles assigned to the user.
  
  
  
  Review Network Settings:
  
  Check for any network issues that may be affecting communication between the client and the SAP server. Ensure that firewalls are not blocking the necessary ports.
  
  
  
  Consult SAP Notes:
  
  Look for relevant SAP Notes that may address specific issues related to logon tickets. SAP Notes often provide detailed troubleshooting steps and solutions.
  
  
  
  Testing:
  
  After making changes, test the configuration by attempting to log in again using logon tickets. Monitor the system logs for any additional error messages that may provide further insight.
  
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for detailed information on configuring logon tickets and SSO.
  SAP Community: Engage with the SAP Community forums to seek advice from other users who may have encountered similar issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as STRUST (for SSL management) and SU01 (for user management) to assist in troubleshooting.
  
  If the issue persists after following these steps, it may be necessary to engage SAP support for further assistance.