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 |
|---|---|---|---|---|---|
| WB002 | Error | 2182 | -241L | "Database backup not started" | A database backup could not be started. Either a backup is already running, or you do not have the required authority (BACKUP, DBA, or REMOTE DBA). Click here for a list of possible parameters and odbc states. |
| WB003 | Error | 2183 | -242L | "Incomplete transactions prevent transaction log renaming" | The last page in the transaction log was read by a call to db_backup. One or more currently active connections have partially completed transactions, preventing the transaction log file from being renamed. Reissue the db_backup call. Click here for a list of possible parameters and odbc states. |
| WB004 | Error | 2184 | -243L | "Unable to delete database file" | You attempted to delete a database file, but it could not be deleted. The file name should not be the same as any database file that is currently in use. Click here for a list of possible parameters and odbc states. |
| WB005 | Error | 2185 | -244L | "Transaction log was truncated" | An operation was being performed on the transaction log such as SQL Remote or Replication Agent processing and the transaction log was truncated by an independent backup during that operation. Click here for a list of possible parameters and odbc states. |
| WB006 | Error | 2344 | -715L | "Contents of backup files are inconsistent" | During a RESTORE, the contents of a backup that was done to two or more disk or tape devices were found to be inconsistent. Click here for a list of possible parameters and odbc states. |
| WB007 | Error | 2345 | -716L | "Backup file format is invalid" | The format of an archive file to be used during a RESTORE is invalid. Click here for a list of possible parameters and odbc states. |
| WB008 | Error | 2346 | -717L | "RESTORE unable to open file '%1'" | RESTORE was unable to open one of the database files. Click here for a list of possible parameters and odbc states. |
| WB009 | Error | 2347 | -718L | "RESTORE unable to write to file '%1'" | RESTORE was unable to write to one of the database files. Click here for a list of possible parameters and odbc states. |
| WB010 | Error | 2348 | -719L | "RESTORE unable to start database '%1'" | After a RESTORE, the resulting database could not be started. Click here for a list of possible parameters and odbc states. |
| WB011 | Warning | 2412 | 119L | "Unable to open backup log '%1'" | The server was unable to open the backup log to record the execution of a BACKUP or RESTORE statement. Check the settings of the environment variables used to locate the backup log file. The directory to contain the log must already exist. Click here for a list of possible parameters and odbc states. |
| WB012 | Error | 2631 | -967L | "Backup file '%1' already exists" | A file that would normally be created by this BACKUP statement already exists. Click here for a list of possible parameters and odbc states. |
| WB013 | Error | 2689 | -1021L | "Invalid backup operation" | The specified backup operation is not valid because of previous backup operation(s). Click here for a list of possible parameters and odbc states. |
| WB014 | Error | 2697 | -1028L | "Connection attempting BACKUP has uncommitted transactions" | A connection attempting to perform a BACKUP ... WAIT BEFORE START or BACKUP ... WAIT AFTER END has uncommitted transactions. A COMMIT or ROLLBACK must be performed before executing the backup. Click here for a list of possible parameters and odbc states. |
| WB015 | Error | 2714 | -1045L | "Invalid backup parameter value" | One or more of the parameters supplied to the backup operation has an invalid value. Click here for a list of possible parameters and odbc states. |
| WB016 | Error | 2726 | -1057L | "BACKUP clause '%1' conflicts with '%2'" | Clauses specified in the BACKUP STATEMENT are mutually exclusive. Click here for a list of possible parameters and odbc states. |
| WB017 | Error | 2748 | -1079L | "Backup is unable to open database file '%1'" | The database file can not be opened by the backup. It may have been erased or otherwise corrupted. Click here for a list of possible parameters and odbc states. |
| WC001 | Error | 2518 | -868L | "'%1' is an unknown character set encoding label" | The specified character set label is not recognized, so conversion from/to that character set is not possible. Click here for a list of possible parameters and odbc states. |
| WC002 | Error | 2520 | -870L | "Cannot convert between requested character set '%1' and database character set '%2'" | The server is unable to convert between the connection character set that was specified and the database character set. This could happen when the dbicu and dbicudt DLLs are not installed. Click here for a list of possible parameters and odbc states. |
| WC003 | Error | 2536 | -879L | "An invalid multi-byte input character was encountered when converting from %1 to %2" | While the server was performing character set conversion on an input string, an invalid multi-byte character was encountered. The operation was aborted. Click here for a list of possible parameters and odbc states. |
| WC004 | Error | 2866 | -1189L | "The UTF-16 endian specified does not match the Byte Order Mark found in the data" | The specified UTF-16 encoding explicitly specifies the expected endian of the data; however, the Byte Order Mark found at the beginning of the data indicates that the data is encoded in the opposite endian. Click here for a list of possible parameters and odbc states. |