14
Login failed.
This error occurs when a login request is rejected by Adaptive Server.
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.
The user is trying to log in to an Adaptive Server:
That does not exist, or
To which the user does not have access, or
That is not running.
Adaptive Server is in single-user mode and only “sa” can login.
Adaptive Server shutdown is in progress and only “sa” can login.
Remote Adaptive Server names are translated from the login record to a site ID. If the Adaptive Server 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 Adaptive Server password.
Determine whether any of the reasons listed above are causing the error. If you have checked each of these and you still cannot log in to Adaptive Server, call Sybase Technical Support.
Following are instructions for checking on the above reasons:
Login name does not exist in syslogins (names are case-sensitive).
When Adaptive Server is first installed, the only login is “sa” and it has no password.
If using isql, make sure the user is specifying the -U option and that the correct name and case are being specified.
Check syslogins to make sure the user is spelling the login name correctly:
1> select * from syslogins 2> go
An incorrect password has been entered (passwords are case-sensitive).
If using isql, make sure the user is specifying the -P option and the correct password and case are being specified.
If a user cannot remember his or her password:
Change the password using sp_password (only the System Security Officer (SSO) can change someone else's password):
1> sp_password <caller_passwd>, 2> <new_passwd>, <login_name> 3> go
Where <caller_passwd> is the password of the login account that is currently executing sp_password and <new_passwd> is the new password for <login_name> (the name of the user whose password is being changed).
If you cannot remember your “sa” password and you cannot get into Adaptive Server with any other login:
Run dataserver -p to generate a new password for a System Security Officer’s account.
Start Adaptive Server with -p.
Immediately log in to Adaptive Server with the new random password, and execute sp_password to reset your password to a more secure one.
Refer to the Adaptive Server Enterprise core manuals for more information.
The account for the user trying to log in is locked. To determine whether this is the case, type:
1> sp_displaylogin <login_name> 2> go
Where <login_name> is the login name of the user. Check the value for the status column:
If the value is 1, the password is less than 6 characters or NULL.
If the value is 2, the account is locked.
If the value is 3, the account is expired.
To unlock a user account:
1> sp_locklogin <login_name> "unlock" 2> go
(Only System Administrators and System Security Officers can use sp_locklogin to lock and unlock logins.)
The user is trying to log into a server that does not exist or to which the user does not have access. Check the user’s environment file to make sure the value of DSQUERY is defined as the server to which the user is trying to log on.
When Adaptive Server is in single-user mode, only “sa” can login.
Refer to “Returning Adaptive Server to multiuser mode” in the chapter “Server Recovery Tasks” in the most recent version of Troubleshooting and Disaster Recovery.
Check your runserver file to make sure the -m option is not specified.
When Adaptive Server shutdown is in progress, only “sa” can login. Tell the user to wait until Adaptive Server has come back up.
Remote server names are translated from the login record to a site ID. If the server name is not found in sysservers, then the login fails. Use sp_helpserver to list the servers in sysservers.
If a remote login is being attempted and sysremotelogins is missing, then the login fails. To determine whether this is the case, type:
1> sp_helpdb sysremotelogins 2> go
If a remote login is being attempted and the user cannot be found in sysremotelogins, then the login fails. To determine whether this is the case, type:
1> sp_helpremotelogin 2> go
For “sa,” your Replication Server password is different from your Adaptive Server password. Make sure the “sa” passwords are the same.
For information about logins and the procedures mentioned in this write-up, refer to the System Administration Guide: Volume 1 chapter “Introduction to Security” and the subsequent security chapters in that guide.
All versions
