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 |
|---|---|---|---|---|---|
| WW024 | Error | 2385 | -740L | "The communications environment could not be created" | The communications environment could not be created. Either there are insufficient resources to create the environment or the language resource file cannot be found. Click here for a list of possible parameters and odbc states. |
| WW025 | Error | 2455 | -808L | "An internal error was generated by the test harness" | An internal error was generated by the test harness. Click here for a list of possible parameters and odbc states. |
| WW026 | Error | 2465 | -818L | "Version 'V%1' interface used by external function call '%2' is not supported for execution in the current context." | You attempted to call an external function. The attempt to load the associated library failed because of incompatibility with the server. Incompatibility may arise because the dynamic library is using an external function API that is either not supported by the server or is newer than the one supported by the server. It may also arise if the external API is not compatible with the data in the current context. Click here for a list of possible parameters and odbc states. |
| WW027 | Error | 2475 | -828L | "A conflict with the dbmlsync download phase was detected" | Dbmlsync uses this error to detect download phase conflicts with rows modified by other connections. Click here for a list of possible parameters and odbc states. |
| WW028 | Error | 2509 | -860L | "At least one of the specified dbspaces was not calibrated" | You attempted to calibrate a dbspace that was not open or was too small. Click here for a list of possible parameters and odbc states. |
| WW029 | Error | 2606 | -942L | "A workload capture (%1) is already in progress" | You have tried to initiate a workload capture when one is already in progress. You need to wait for the other capture to complete. Click here for a list of possible parameters and odbc states. |
| WW030 | Error | 2607 | -943L | "No workload capture currently exists" | You have tried to stop, pause, resume, or get the status of a workload capture, but no workload captures exist. Click here for a list of possible parameters and odbc states. |
| WW031 | Error | 2615 | -951L | "Cannot access schema file '%1'" | UltraLite requires a schema file to perform the current operation. Either no schema file was specified or the one specified was not accessible or was corrupt. Click here for a list of possible parameters and odbc states. |
| WW032 | Error | 2616 | -952L | "The status of the last synchronization upload is unknown" | The status of the last synchronization upload is unknown. The current operation cannot proceed until a successful upload is synchronized. Click here for a list of possible parameters and odbc states. |
| WW033 | Error | 2617 | -953L | "A schema upgrade is not currently allowed" | A schema upgrade cannot proceed because of concurrent use of the database. For example, all cursors must be closed before a schema upgrade can occur. Click here for a list of possible parameters and odbc states. |
| WW034 | Error | 2618 | -954L | "The database '%1' was not found" | The named database was not found. Ensure your connection string properly names the desired database. Click here for a list of possible parameters and odbc states. |
| WW035 | Error | 2619 | -955L | "This connection already exists" | A connection with the given SQLCA and name (or no name) already exists. Before connecting you must disconnect the existing connection, or specify a different connection name. Click here for a list of possible parameters and odbc states. |
| WW036 | Error | 2620 | -956L | "Information for synchronization is incomplete or invalid, check '%1'" | Information for synchronization is incomplete or invalid. Correct the indicated parameter before attempting to synchronize again. If 'init_verify' is indicated, the InitSyncInfo function was not called. Click here for a list of possible parameters and odbc states. |
| WW037 | Error | 2623 | -959L | "Compression error: %1" | An error occurred during compression. Click here for a list of possible parameters and odbc states. |
| WW038 | Error | 2624 | -960L | "Decompression error: %1" | An error occurred during decompression. Click here for a list of possible parameters and odbc states. |
| WW039 | Error | 2625 | -961L | "Input string is not base64-encoded" | An error occurred during base64 decoding. Click here for a list of possible parameters and odbc states. |
| WW040 | Warning | 2635 | 133L | "UltraLite connection was restored" | The connection attempt completed successfully and the transaction was restored from a suspended state. Click here for a list of possible parameters and odbc states. |
| WW041 | Warning | 2636 | 134L | "UltraLite cursor (or result set or table) was restored" | The cursor (or result set or table) was opened successfully and the cursor position was restored from the suspended state. Click here for a list of possible parameters and odbc states. |
| WW042 | Error | 2637 | -971L | "Checksums are not enabled in this database" | An attempt was made to perform checksum validation but the database does not have checksums enabled. Click here for a list of possible parameters and odbc states. |
| WW043 | Error | 2640 | -974L | "File I/O failed for '%1'" | An error occurred while trying to access the file. If the file is located on a removable media card, the card may have been removed. Click here for a list of possible parameters and odbc states. |