How To Fix SIAG_MSG173 - User logon no longer possible - too many failed attempts

SAP Error Message - Details

• Message type: E = Error

• Message class: SIAG_MSG - GRC Plug-Ins message class

• Message number: 173

• Message text: User logon no longer possible - too many failed attempts

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 SIAG_MSG173 - User logon no longer possible - too many failed attempts ?

  The SAP error message SIAG_MSG173 indicates that a user has exceeded the maximum number of allowed failed login attempts. This is a security feature designed to prevent unauthorized access to the system. When a user fails to log in multiple times (the exact number can vary based on system configuration), the account is locked, and the user receives this error message.
  Cause:
  
  Incorrect Password: The most common cause is that the user is entering the wrong password multiple times.
  Account Lockout Policy: The system is configured to lock accounts after a certain number of failed login attempts to enhance security.
  User Confusion: The user may have forgotten their password or is using an old password that has since been changed.
  Automated Login Attempts: Sometimes, automated scripts or applications may attempt to log in with incorrect credentials, leading to account lockout.
  
  Solution:
  
  
  Unlock the User Account:
  
  An administrator can unlock the user account using transaction code SU01 (User Maintenance).
  Navigate to the user account, and in the "Logon Data" tab, check the "Lock" status and unlock the account.
  
  
  
  Reset Password:
  
  If the user has forgotten their password, the administrator can reset it through the same transaction (SU01) or the user can use the password reset functionality if available.
  
  
  
  Check Security Settings:
  
  Review the security settings related to user logon attempts. This can be done in transaction RZ11 to check the parameter login/failure_count and login/failure_delay to understand the lockout policy.
  
  
  
  Educate Users:
  
  Inform users about the importance of entering the correct credentials and the consequences of multiple failed attempts.
  
  
  
  Monitor Login Attempts:
  
  Use transaction SM20 (Security Audit Log) to monitor failed login attempts and identify any patterns or potential security issues.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to user management and security for any updates or specific configurations that may apply to your version of SAP.
  User Management Best Practices: Implement best practices for user management, including regular password updates, user training, and monitoring of user activity.
  System Configuration: Review the system configuration for user authentication and security policies to ensure they align with organizational security standards.
  
  If the issue persists or if there are additional complications, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.