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 |
|---|---|---|---|---|---|
| WW075 | Error | 2774 | -1103L | "No partial download was found" | A partial download was not found for the synchronizing user. This error could occur if trying to resume from a non-existent partial download or trying to rollback a non-existent partial download. Click here for a list of possible parameters and odbc states. |
| WW077 | Error | 2777 | -1106L | "Too many publications specified for operation" | You have specified too many publications for the required operation. For example, when retrieving the last download timestamp, you are only allowed to select one publication. Click here for a list of possible parameters and odbc states. |
| WW078 | Error | 2779 | -1108L | "Unable to access the filesystem on the device" | On a Palm device, you have tried to utilize the VFS filesystem, but that feature has not been enabled on the device. Click here for a list of possible parameters and odbc states. |
| WW079 | Error | 2780 | -1109L | "Unable to perform requested operation since this database uses keyless encryption" | The operation you requested on the encryption key failed since the UltraLite database uses keyless encryption. This can occur when you try to change the encryption key for a keyless encrypted database. Click here for a list of possible parameters and odbc states. |
| WW080 | Error | 2781 | -1110L | "Synchronization process was unable to re-enter synchronization" | Synchronization was unable to be re-entered by the sync process. This could be caused by two different threads trying to make a synchronize call at the same time. Click here for a list of possible parameters and odbc states. |
| WW081 | Error | 2782 | -1111L | "Information for synchronization was not provided" | You must supply information for synchronization, either directly in the synchronization call or by using the SetSynchInfo call before synchronizing. In the Palm HotSync conduit, this error occurs during synchronization if you have not used the SetSynchInfo call in your application before exiting, or if the SetSynchInfo call failed. Click here for a list of possible parameters and odbc states. |
| WW082 | Error | 2783 | -1112L | "Specified file system volume not found for database '%1'" | The file system volume you specified in the database file name was not found. Check the volume name or ordinal. Click here for a list of possible parameters and odbc states. |
| WW083 | Error | 2789 | -1117L | "A row cannot be stored because it exceeds the database page size" | You attempted to insert or update a row which is too large to be stored on a database page. For UltraLite, with the exception of BLOB columns, a row must fit entirely on a single database page. Larger page sizes may be used to accommodate larger rows. Click here for a list of possible parameters and odbc states. |
| WW084 | Error | 2794 | -1122L | "Exceeded maximum of '%1' allowable parameters" | The maximum allowable parameters for the given web client procedure or function has been exceeded . Click here for a list of possible parameters and odbc states. |
| WW085 | Error | 2795 | -1123L | "Invalid mime type '%1'" | The mime type specifier is invalid. Click here for a list of possible parameters and odbc states. |
| WW086 | Error | 2801 | -1129L | "The '%1' attribute contains mismatched parentheses within '%2'" | The value of the attribute is not valid due to mismatched parenthesis (or possibly braces if specifying a port option). Click here for a list of possible parameters and odbc states. |
| WW087 | Error | 2802 | -1130L | "The '%1' attribute is missing a comma within '%2'" | The value of the attribute is not valid due to a missing comma. Click here for a list of possible parameters and odbc states. |
| WW088 | Error | 2803 | -1131L | "The attribute '%1' sets an option '%2' that is incompatible with '%3'" | The options specified for this attribute are not compatible. Click here for a list of possible parameters and odbc states. |
| WW089 | Error | 2804 | -1132L | "Maximum row size for table '%1' would be exceeded" | You tried to create or alter a table with a maximum row size greater than 64KB. In UltraLite, tables must be defined such that the maximum row size (the sum of the bytes required to store each column) is less than 64KB. Click here for a list of possible parameters and odbc states. |
| WW090 | Error | 2811 | -1138L | "The mirror '%1' does not match database '%2'" | The named mirror file does not correspond to the database file. This could happen if the database was not shut down properly, or if the wrong mirror file was specified. The mirror file must be moved or discarded before proceeding, or a different mirror specified. Click here for a list of possible parameters and odbc states. |
| WW091 | Error | 2826 | -1150L | "The SQL scripts DLL cannot be loaded" | The SQL scripts DLL cannot be loaded. The DLL might be missing or the version found might not match the version of the database server being used. Click here for a list of possible parameters and odbc states. |
| WW092 | Error | 2848 | -1171L | "Client application does not allow transfer of data ('%1')" | The client application does not allow the transfer of server initiated data. In order to allow transfer of server initiated data, the application must register a validation callback mechanism with the client library. Click here for a list of possible parameters and odbc states. |
| WW093 | Error | 2849 | -1172L | "Client application disallowed the transfer of data ('%1')" | The client application rejected the transfer of server initiated data. In order to allow transfer of server initiated data, the application registered a validation callback which rejected the transfer of requested data. Click here for a list of possible parameters and odbc states. |
| WW094 | Error | 2850 | -1173L | "Client library reported an error accessing data during transfer ('%1')" | The client application reported an error while attempting to access the data for a transfer request from the server. Reasons could include the client application lacking permissions to the data object or other operating system reported errors. Click here for a list of possible parameters and odbc states. |
| WW095 | Error | 2855 | -1178L | "Transaction log mirroring cannot be used with database mirroring" | Transaction log mirroring cannot be used with database mirroring. Use the DBLOG utility to disable transaction log mirroring. Click here for a list of possible parameters and odbc states. |