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 |
|---|---|---|---|---|---|
| WC005 | Error | 2540 | -881L | "Character substitution was required when converting from %1 to %2" | While the server was performing character set conversion on an input string, some characters could not be represented in the database character set. The operation was aborted. See on_charset_conversion_failure option. Click here for a list of possible parameters and odbc states. |
| WC007 | Error | 2544 | -883L | "Character conversion error or warning report is not available when the single-byte converter is used" | You attempted to set the on_charset_conversion_failure option to produce either a warning or error report. This setting is not available when the single-byte to single-byte converter is used. Click here for a list of possible parameters and odbc states. |
| WC008 | Error | 2554 | -891L | "Cannot convert between requested character sets '%1' and '%2'" | The server is unable to convert between the two specified character sets. This could happen when the dbicu and dbicudt DLLs are not installed. Click here for a list of possible parameters and odbc states. |
| WC009 | Error | 2741 | -1072L | "'%1' is not a valid character set encoding for use with collation '%2'" | The specified character set cannot be used with the specified collation. Click here for a list of possible parameters and odbc states. |
| WC010 | Error | 2742 | -1073L | "'%1' cannot be used as the NCHAR collation: only UCA and UTF8BIN may be used" | The specified collation cannot be used as the NCHAR collation. NCHAR always uses UTF-8, so the collation must be either UCA or UTF8BIN. Click here for a list of possible parameters and odbc states. |
| WC011 | Error | 2744 | -1075L | "Failed to convert from character set '%1' to '%2'" | The server failed to convert between the two specified character sets. This could happen when the dbicu and dbicudt DLLs are not installed. Click here for a list of possible parameters and odbc states. |
| WC012 | Error | 2745 | -1076L | "dbicu libraries are required but not installed" | The server is unable to load ICU components that are required by this database. Ensure that the dbicu and dbicudt DLLs are installed. Click here for a list of possible parameters and odbc states. |
| WC013 | Error | 2787 | -1116L | "Collation '%1' not supported on this platform" | The specified collation is not supported on the current platform. Click here for a list of possible parameters and odbc states. |
| WC014 | Error | 2796 | -1124L | "The dbicu library and server versions do not match." | The server is unable to load ICU components that are required by this database. Ensure that the correct version of the dbicu libraries are installed. Click here for a list of possible parameters and odbc states. |
| WC015 | Error | 2813 | -1140L | "Unable to start database \"%1\": CHAR collation or tailoring not supported on this platform" | The specified CHAR collation is not supported on the current platform. Click here for a list of possible parameters and odbc states. |
| WC016 | Error | 2814 | -1141L | "Unable to start database \"%1\": NCHAR collation or tailoring not supported on this platform" | The specified NCHAR collation is not supported on the current platform. Click here for a list of possible parameters and odbc states. |
| WC017 | Error | 2818 | -1144L | "'%1' cannot be used as the encoding specification for '%2' data" | The specified encoding cannot be used for interpreting the given data. For CHAR data, the encoding must be the database's CHAR character encoding and for NCHAR data, it must be the database's NCHAR character encoding. Click here for a list of possible parameters and odbc states. |
| WE001 | Error | 2418 | -771L | "Event '%1' not found" | You have attempted to reference an event with a name that does not exist in the database. Click here for a list of possible parameters and odbc states. |
| WE002 | Error | 2419 | -772L | "Event '%1' already exists" | You have attempted to create an event with a name that already exists in the database. Click here for a list of possible parameters and odbc states. |
| WE003 | Error | 2420 | -773L | "Schedule '%1' for event '%2' not found" | You have attempted to reference a schedule with a name that does not exist in the database for the named event. Click here for a list of possible parameters and odbc states. |
| WE004 | Error | 2421 | -774L | "Schedule '%1' for event '%2' already exists" | You have attempted to create a schedule with a name that already exists in the database for the named event. Click here for a list of possible parameters and odbc states. |
| WE005 | Error | 2438 | -791L | "Invalid day of week or month '%1' for event '%2'" | You have attempted to create a schedule with an invalid day-of-week name or day-of-month number. Click here for a list of possible parameters and odbc states. |
| WE006 | Error | 2439 | -792L | "Invalid time '%1' for event '%2'" | You have attempted to create a schedule with an invalid start or stop time. Click here for a list of possible parameters and odbc states. |
| WE007 | Error | 2440 | -793L | "Invalid start date/time for event '%1'" | You have specified an event starting date that is invalid. Click here for a list of possible parameters and odbc states. |
| WE008 | Error | 2453 | -806L | "System event type '%1' not found" | You have attempted to create an event with a system event type name that does not exist in the database. Click here for a list of possible parameters and odbc states. |