This section contains general error messages for the Adaptive Server dataserver utility program.
11
Cannot open default database ’%.*s’.
This error is raised when Adaptive Server is unable to open the user’s default database at login.
After raising the error, the server checks if the user is allowed to log in to master. If the master database is forbidden, the login request is denied.
Common reasons why the default database cannot be opened include:
The database may not be available for use. For example, it may be in recovery.
The database may be up, but not available for general use. For example, it may be undergoing failover as part of the High Availability (HA) subsystem (Version 12.0).
Permission checks failed. For example, if the database was created by loading from another server, but the login information in source and target servers does not match, login may fail.
Retry the login in the event that the database was in recovery or temporarily unavailable.
Since the 4001 error is usually a symptom of some other problem, check the server error log for any other errors that may have been raised prior to 4001. Check for the following errors and retry:
921 errors (Database ’%.*s’ has not been recovered yet - please wait and try again.) indicate that the database is in recovery, or is marked suspect due to an earlier problem. Refer to the Error 921 writeup in this manual for instructions.
2206 errors (Database %.*s with dbid %d is already shut down.) indicate that the database is not available for general use. These errors are raised in Version 12.0 and higher. Check for other HA subsystem messages to determine the cause.
10351 errors (Server user id %d is not a valid user in database ’%.*s’) indicate a permissions problem. If the database was loaded from another server, the problem may be due to an incorrect suid/uid combination in sysusers. Check syslogins entries in source and target server, respectively. Check the Security Administration Guide and “mismatched suids” in the System Administration Guide for more information.
All versions
14
Login failed.
This error occurs when a login request is rejected by Adaptive Server.
Some reasons for Error 4002 are:
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
the user does not have access to, or
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 4002 error. If you have checked each of these and you still cannot login 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 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 you are changing).
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. You start Adaptive Server with -p, immediately log into 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 utility programs manual for details.
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 that the user does not have access to. Check the user's environment file to make sure the value of DSQUERY is defined to be the Server the user is trying to log in to.
When Adaptive Server is in single-user mode, only “sa” can login.
Refer to “Returning Adaptive Server to Multiuser Mode” in the Encyclopedia of Tasks chapter.
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 writeup, refer to the Security Administration Guide.
All versions
20
While reading characters from the client, the receiving buffer has been detected to be too small.
All client/server communication occurs over a network via packets. Clients initiate a connection to the server. The connection sends client requests and server responses.
Error 4020 is raised when the server detects an overflow in the destination buffer while reading one or more characters from the client. The error breaks the connection to the server.
Possible reasons for Error 4020 include:
application errors
corrupt packets being transmitted
incorrect network configuration
Collect all relevant information about the circumstances in which the error occurred: character set differences on client and server, changed or new applications, recent changes in the network configuration, and so on.
Check for coding errors in the application which may be causing incorrectly sized packets to be sent.
Check for possible packet corruption within the network.
Check the network configuration. For example, if there is 7-bit communication at one end, and 8-bit at the other end, check that the network is properly configured to handle this setup.
Check that Adaptive Server is correctly configured to work with the underlying network packet size or buffer size on your system. Relevant server parameters include:
default network packet size maximum network packet size total memory
All versions
