Server Error Messages 4000 – 4099

Number

Severity

Text and Explanation

4001

11

 Cannot open default database `%.*s'.

Explanation: Command failed. Check syntax and your Adaptive Server environment.

4002

14

 Login failed.

Explanation: Refer to the writeup for this error.

4013

14

 Login failed - not a secure SQL Server.

Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.

4016

16

 Language name in login record `%.*s' is not an official name on this SQL Server.  Using default `%.*s' from syslogins instead.

Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.

4017

16

 Neither language name in login record `%.*s' nor language name in syslogins `%.*s' is an official language name on this SQL Server.  Using server-wide default `%.*s' instead.

Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.

4018

16

 Your default language name from syslogins `%.*s' is not an official language name on this SQL Server.  Using server-wide default `%.*s' instead.

Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.

4019

16

 Default date order `%.*s' for language `%.*s' is invalid.  Using `mdy' instead.

Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.

4020

20

 While reading characters from the client, the receiving buffer has been detected to be too small.

Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.

4022

10

The password has expired, but you are still allowed to log in. You must change your password before you can continue. If a login trigger is set, it will not be executed.

Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.

4023

10

 Your password will expire in %s days.

Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.

4024

10

 The packet size (%d) specified at login time is illegal. Legal values are between 512 and %d.

Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.

4025

10

 A serious error was encountered while attempting to increase the packet size specified for spid %d. The Network memory map maybe corrupt. Call Technical Support for further assistance.

Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.

4050

11

Component Integration Services not enabled or not installed.

Explanation: Command failed. Check your Adaptive Server environment.

4051

14

Security Control Layer has not been initialized. Security session cannot be established.  

Explanation:

4052

14

Failed to allocate data structure for use by the Security Control Layer. Cannot establish a security session. 

Explanation:

4053

14

Security session setup failed during security session establishment.  

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action.

4054

14

Protocol negotiation failed during security session establishment.  

Explanation:

4055

14

Unified Login through the underlying security mechanism is required to connect to the SQL Server. 

Explanation:

4056

16

Login name %.*s not found. Check and make sure an entry exists in Syslogins.  

Explanation: You used an invalid login name. Check that the name exists in syslogins.

4057

16

Login name %.*s not a user in the current database.

Explanation: Check login and working database context.

4058

16

Login currently under set session authorization. It is required to go back to the original identity before performing another set session authorization. 

Explanation: You can only assume another identity from the original identity.

4059

16

Set session authorization requires a target identity. Please specify a valid login name. 

Explanation: Check for missing information in query.

4060

16

Login name not found for suid %d. Check and make sure an entry exists in Syslogins. 

Explanation: Check the syslogins system table.

4061

10

The SQL Server is using the default authentication information file for it's authentication information. 

Explanation: This is an informational message.

4062

10

Some of the requested security services are not supported by the underlying security mechanism. Please contact a user with SSO_ROLE. 

Explanation: This is an informational message but may require action as indicated.

4063

10

Security services being used for this connection are inadequate as per the SQL Server's security configuration requirements. Please contact a user with SSO_ROLE. 

Explanation: You may be logging in to Adaptive Server via an insecure connection.

4064

16

Invalid security service requested.  

Explanation: Invalid or incorrect connection context. Contact a user with System Security Officer (SSO) role.

4066

16

Login account %.*s is locked. Please contact a person with SA or SSO role.  

Explanation: Contact the System Administrator to resolve the login security issue.

4067

14

Login failed because an incorrect password was supplied.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4068

14

HA Login failed. Session handle not found (sys:%d ses:%d).

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4069

14

HA Login failed. Session handle issued to different user: ’%.*s’. 

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4070

14

HA Login failed. There is no failover in progress.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4071

14

HA Login failed. Failover timeout.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4072

14

HA Login failed. Failback timeout.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4073

14

HA Login failed. Server not in HA primary configuration. 

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4074

14

HA Login failed. Server not in HA secondary configuration. 

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4075

16

’enable enterprise java beans’ option not set.

Explanation: Set the specified option to continue.

4076

16

EJB Config Error : SYBASE environment variable not set.

Explanation: Check your Adaptive Server environment.

4077

16

 EJB Config Error : SYBASE_EJB environment variable not set.

Explanation: Check your Adaptive Server environment.

4078

16

Enterprise java bean server is up and running.

Explanation: This is an informational message.

4079

16

 Enterprise java bean server is down.

Explanation: This is an informational message. You may need to restart the EJB server.

4080

16

Enterprise java bean server not started since the auto start option is not enabled.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4081

16

Enterprise java bean server not started since no EJB server has been configured.

Explanation: Check your EJB documentation to configure the server.

4082

16

EJB Config Error : Could not obtain the directory where the krg file is located

Explanation: Check your EJB environment.

4083

16

 Unable to open the ASE krg file

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4084

16

Unable to create the krg file for the ejb server

Explanation: Command failed due to invalid or illegal request.

4085

16

 Unable to write %d bytes into the ejb server krg file

Explanation: Command failed due to invalid or illegal request.

4086

16

 Could not execute login script for user %.*s

Explanation: Command failed due to invalid or illegal request.

4087

16

 Unable to open ejb server property file %s.

Explanation: Command failed due to invalid or illegal request.

4088

16

 Unable to open the listener property file %s.

Explanation: Command failed due to invalid or illegal request.

4089

10

Need to have a valid java license and the ’enable enterprise java beans’ option set to execute this command

Explanation: Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4090

10

There is no valid license for ASE_EJB hence the EJB Server feature is not enabled.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4091

10

The ’enable enterprise java beans’ configuration option needs to be set to execute this command.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4092

10

The ’enable enterprise java beans’ configuration option needs to be set to execute this command.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.

4093

10

 SSL Plus security modules loaded successfully.\n

Explanation: This is an informational message.

4094

16

 The Enterprise Java Bean feature is not supported on this platform.

Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action.