Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 08W03 | Error | 2038 | -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 specified in your license agreement. The server may be running low on cache, and as a result 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. |
| 08W04 | Error | 2035 | -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. |
| 08W05 | Error | 2043 | -106L | "Cannot open transaction log file -- %1" | The database server was unable to open the named transaction log file. The transaction log file name may include an invalid device or directory. If this is the case, you can use the Transaction Log utility (dblog) to find out where the transaction log should be and perhaps change it. Click here for a list of possible parameters and odbc states. |
| 08W06 | Error | 2046 | -109L | "There are still active database connections" | You attempted to shut down a database that still has active connections. Click here for a list of possible parameters and odbc states. |
| 08W07 | Error | 2011 | -80L | "Unable to start database server" | It was not possible to start the database server. There may not be enough memory to run the database server. It may also be that the executable cannot be found. Click here for a list of possible parameters and odbc states. |
| 08W08 | Error | 2012 | -81L | "Invalid database server command line" | It was not possible to start the database server because the command line was invalid. Click here for a list of possible parameters and odbc states. |
| 08W09 | Error | 2018 | -82L | "Unable to start specified database: %1" | The database server was unable to start the specified database. Check the database server messages window for more details. If the server was being started automatically, you can use the database server -o option to view messages from the database server or start the server manually to try to obtain more information about why the database cannot be started. Click here for a list of possible parameters and odbc states. |
| 08W10 | Error | 2019 | -83L | "Specified database not found" | The database server was unable to find the specified database. The database server may be attempting to start a database file that cannot be opened or that cannot be found on the network. You may be attempting to connect to a database name that is not running. Click here for a list of possible parameters and odbc states. |
| 08W11 | Error | 2020 | -84L | "Specified database is invalid" | The database file you specified is invalid. The database server is stopped. Click here for a list of possible parameters and odbc states. |
| 08W12 | Error | 2022 | -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. |
| 08W13 | Error | 2025 | -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. |
| 08W14 | Error | 2026 | -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. |
| 08W15 | Error | 2027 | -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. |
| 08W16 | Error | 2029 | -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. |
| 08W17 | Error | 2044 | -107L | "Error writing to transaction log file" | The database server got an I/O error writing the transaction log file. The disk may be full or the log file name could be invalid. Click here for a list of possible parameters and odbc states. |
| 08W18 | Error | 2178 | -230L | "sqlpp/dblib version mismatch" | Your executable has Embedded SQL source files that were preprocessed with a version of sqlpp that does not match the database interface library. Click here for a list of possible parameters and odbc states. |
| 08W19 | Error | 2179 | -231L | "Client/database server version mismatch" | Your executable uses a database interface library that does not match the version number of the database server. Click here for a list of possible parameters and odbc states. |
| 08W20 | Error | 2845 | -985L | "The database name 'utility_db' is reserved for the utility database." | You are attempting to start a database with the name "utility_db". This name is reserved for the utility database. Click here for a list of possible parameters and odbc states. |
| 08W21 | Error | 2034 | -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. |
| 08W22 | Error | 2031 | -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. |