Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2021 | Error | 08W39 | -72L | "No database file specified" | The database server was started but there was no specified database file. The server is stopped. Click here for a list of possible parameters and odbc states. |
| 2022 | Error | 08W12 | -85L | "Communication error" | There is a communication problem between the application and the server. Click here for a list of possible parameters and odbc states. |
| 2024 | Error | 08W26 | -78L | "Dynamic memory exhausted" | A failure occurred when the database server was trying to allocate dynamic memory. Click here for a list of possible parameters and odbc states. |
| 2025 | Error | 08W13 | -86L | "Not enough memory to start" | The database server started, but stopped because there was not enough memory. Click here for a list of possible parameters and odbc states. |
| 2026 | Error | 08W14 | -87L | "Database name required to start server" | You did not supply a database name. A database name is required to start a database server. Click here for a list of possible parameters and odbc states. |
| 2027 | Error | 08W15 | -88L | "Client/server communications protocol version mismatch" | The connection failed because the protocol versions of the client and the server do not match. Ensure the client and server software are the same version. Click here for a list of possible parameters and odbc states. |
| 2028 | Error | 08W23 | -96L | "Database server already running" | The database server was not able to start because a server with the same name was already running. Click here for a list of possible parameters and odbc states. |
| 2029 | Error | 08W16 | -89L | "Database server not running in multi-user mode" | The database server was started for bulk loading (the -b option) and cannot be used as a network server. Stop the database server, and start again without -b. Click here for a list of possible parameters and odbc states. |
| 2030 | Error | 08W24 | -735L | "Invalid parameter" | An error occurred while evaluating a parameter. Click here for a list of possible parameters and odbc states. |
| 2031 | Error | 08W22 | -97L | "Database page size too big: %1" | You attempted to start a database with a page size that exceeds the maximum page size of the running server. Either restart the server and include this database name on the command line, or restart the server with the required page size. Click here for a list of possible parameters and odbc states. |
| 2032 | Error | 08W32 | -644L | "Invalid database page size" | You attempted to create a database with an invalid page size. The page size for a SQL Anywhere database must be either 2048, 4096, 8192, 16384, or 32768 bytes. The page size for an UltraLite database must be either 1024, 2048, 4096, 8192, or 16384 bytes. Click here for a list of possible parameters and odbc states. |
| 2033 | Error | 08W33 | -645L | "Database creation failed: %1" | Your attempt to initialize a file for a database failed. Click here for a list of possible parameters and odbc states. |
| 2034 | Error | 08W21 | -98L | "Authentication violation" | You attempted to connect to a server that has been authenticated for exclusive use with a specific application. Click here for a list of possible parameters and odbc states. |
| 2035 | Error | 08W04 | -99L | "Connections to database have been disabled" | Connections to the network database server have been disabled. You will receive this error until connections have been enabled. Click here for a list of possible parameters and odbc states. |
| 2036 | Error | 08W01 | -100L | "Database server not found" | The database server is not running, or is in the process of starting up or shutting down, or the interface library is unable to find it. Click here for a list of possible parameters and odbc states. |
| 2037 | Error | 08003 | -101L | "Not connected to a database" | You are not connected to a database, or you executed the DISCONNECT statement and have not connected to a database again. Click here for a list of possible parameters and odbc states. |
| 2038 | Error | 08W03 | -102L | "Database server connection limit exceeded" | You exceeded the number of computers allowed to connect to the server. If you are running the network database server, the limit is spelled out in your license agreement. The server may be running low on cache such that it cannot accept any more database connections. The personal database server is restricted to 10 connections. Click here for a list of possible parameters and odbc states. |
| 2039 | Error | 28000 | -103L | "Invalid user ID or password" | You supplied an invalid user ID or an incorrect password. Click here for a list of possible parameters and odbc states. |
| 2041 | Error | 28W01 | -104L | "Invalid user ID or password on preprocessed module" | You specified an invalid user ID or password when a module was preprocessed. Click here for a list of possible parameters and odbc states. |
| 2042 | Error | 08001 | -105L | "Database cannot be started -- %1" | The specified database cannot be started. Either it does not exist, it is not a database, it is corrupt, or it is an older, unsupported format. Click here for a list of possible parameters and odbc states. |