SAP Knowledge Base Article - Preview

3685111 - SYB: How to identify the real cause of login failed(Error 4002)

Symptom

  • Error 4002  Login Failed. 

         Explanation
         This error occurs when a login request is rejected by SAP ASE.

  • Some reasons for error 4002 are:
    - The user name does not exist in syslogins (names are case-sensitive).
    - An incorrect password has been entered (passwords are case-sensitive).
    - The account for the user trying to log in is locked.
    - SAP ASE is in single-user mode and only “sa” can login.
    - SAP ASE shutdown is in progress and only “sa” can login.
    - Remote SAP ASE names are translated from the login record to a site ID. If the SAP ASE name is not found in sysservers, then the login fails.
    - A remote login is being attempted and sysremotelogins is missing.
    - A remote login is being attempted and the user cannot be found in sysremotelogins.
    - For “sa,” your Replication Server password is different from your SAP ASE password.

  • How to track the real cause of Error 4002?


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

Error 4002, Login failed, Error 4067, Error 4066, Error 16106 , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.