Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1098 | "A tracing connection is already active" |
|---|---|
Constant | TRACING_ALREADY_ATTACHED |
SAP Sybase Error Number | 2768 |
SQL State | 08W96 |
SQL Code | -1098L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This database is already participating in a tracing connection, either as the sender (the database being traced) or as the receiver (the tracing database). A database can only send or receive one stream of tracing data at a time. |
| Error 1099 | "Transact-SQL outer joins are currently disabled" |
|---|---|
Constant | TSQL_OUTER_JOINS_DISABLED |
SAP Sybase Error Number | 2769 |
SQL State | 55W25 |
SQL Code | -1099L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The ability to specify a Transact-SQL outer join in a query is currently disabled by the setting of the tsql_outer_joins connection option. Transact-SQL outer joins are deprecated in this release of SQL Anywhere. |
| Error 1100 | "The operation failed because column '%1''s type does not support streaming" |
|---|---|
Constant | COLUMN_NOT_STREAMABLE |
SAP Sybase Error Number | 2771 |
SQL State | WW045 |
SQL Code | -1100L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The number of the column whose type is invalid. |
Probable Cause | The only column types that support streaming are: BINARY, LONG BINARY, VARCHAR and LONG VARCHAR. This error could also occur when allocating a stream object twice on the same column. |
| Error 1101 | "Column '%1' not part of any indexes in its containing table" |
|---|---|
Constant | COLUMN_NOT_INDEXED |
SAP Sybase Error Number | 2772 |
SQL State | WW073 |
SQL Code | -1101L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the column not found in any index. |
Probable Cause | The specified column is not part of any indexes belonging to the containing table. |
| Error 1102 | "Unable to retry download because upload is not finished" |
|---|---|
Constant | DOWNLOAD_RESTART_FAILED |
SAP Sybase Error Number | 2773 |
SQL State | WW074 |
SQL Code | -1102L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The MobiLink server could not restart the download because the MobiLink server has not received the entire upload stream. |
| Error 1103 | "No partial download was found" |
|---|---|
Constant | PARTIAL_DOWNLOAD_NOT_FOUND |
SAP Sybase Error Number | 2774 |
SQL State | WW075 |
SQL Code | -1103L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 1104 | "Too many users in database" |
|---|---|
Constant | TOO_MANY_USERS |
SAP Sybase Error Number | 2775 |
SQL State | 54W10 |
SQL Code | -1104L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You have exceeded the maximum number of users permitted to access the database. The maximum number of users that are allowed granted access to a single UltraLite database is four. |
| Error 1106 | "Too many publications specified for operation" |
|---|---|
Constant | TOO_MANY_PUBLICATIONS |
SAP Sybase Error Number | 2777 |
SQL State | WW077 |
SQL Code | -1106L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 1107 | "Too many references to a BLOB" |
|---|---|
Constant | TOO_MANY_BLOB_REFS |
SAP Sybase Error Number | 2778 |
SQL State | 54W11 |
SQL Code | -1107L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You have exceeded the maximum number of references to a particular BLOB. In UltraLite you may have at most 256 references to any one particular BLOB. |
| Error 1108 | "Unable to access the file system on the device" |
|---|---|
Constant | CANNOT_ACCESS_FILESYSTEM |
SAP Sybase Error Number | 2779 |
SQL State | WW078 |
SQL Code | -1108L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | On a Palm device, you have tried to utilize the VFS file system, but that feature has not been enabled on the device. |
| Error 1109 | "Unable to perform requested operation since this database uses keyless encryption" |
|---|---|
Constant | KEYLESS_ENCRYPTION |
SAP Sybase Error Number | 2780 |
SQL State | WW079 |
SQL Code | -1109L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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 database that uses keyless encryption (obfuscation for example). |
| Error 1110 | "UltraLite cannot synchronize because a synchronization is already running" |
|---|---|
Constant | SYNC_NOT_REENTRANT |
SAP Sybase Error Number | 2781 |
SQL State | WW080 |
SQL Code | -1110L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to synchronize an UltraLite database which is already synchronizing. You must wait until the current synchronization completes before starting another. UltraLite allows most operations to run concurrently with synchronization, but only a single synchronization can be active at a time. This is generally caused by two different threads attempting a synchronize call or statement at the same time. |
| Error 1111 | "Information for synchronization was not provided" |
|---|---|
Constant | SYNC_INFO_REQUIRED |
SAP Sybase Error Number | 2782 |
SQL State | WW081 |
SQL Code | -1111L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You must supply information for synchronization in the synchronization call. |
| Error 1112 | "Specified file system volume not found for database '%1'" |
|---|---|
Constant | FILE_VOLUME_NOT_FOUND |
SAP Sybase Error Number | 2783 |
SQL State | WW082 |
SQL Code | -1112L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the database. |
Probable Cause | The file system volume you specified in the database file name was not found. Check the volume name or ordinal. |
| Error 1113 | "Correlation name '%1' is not valid for use with the ROWID function" |
|---|---|
Constant | INVALID_CORRELATION_FOR_ROWID |
SAP Sybase Error Number | 2784 |
SQL State | 42WBF |
SQL Code | -1113L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the invalid correlation name. |
Probable Cause | The correlation name used was not valid for the ROWID function. Only the correlation names of base tables, temporary tables, global temporary tables or proxy tables may be used with the ROWID function. The argument of a ROWID function should not refer to a view, derived table, common table expression, or a procedure. |
| Error 1114 | "Invalid setting for SOAP header '%1'" |
|---|---|
Constant | INVALID_SOAP_HEADER_SETTING |
SAP Sybase Error Number | 2785 |
SQL State | 42W86 |
SQL Code | -1114L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the invalid SOAP header. |
Probable Cause | You supplied an invalid value for a SOAP header. |
| Error 1115 | "Table '%1' contains an invalid reference to the ROWID function" |
|---|---|
Constant | INVALID_ROWID_PLACEMENT |
SAP Sybase Error Number | 2786 |
SQL State | 42WC1 |
SQL Code | -1115L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the table that contains the invalid reference. |
Probable Cause | The ROWID function cannot be used in a computed column expression or in a CHECK constraint. |
| Error 1116 | "Collation '%1' not supported on this platform" |
|---|---|
Constant | COLLATION_NOT_SUPPORTED |
SAP Sybase Error Number | 2787 |
SQL State | WC013 |
SQL Code | -1116L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The collation that is not supported. |
Probable Cause | The specified collation is not supported on the current platform. |
| Error 1117 | "A row cannot be stored because it exceeds the database page size" |
|---|---|
Constant | ROW_EXCEEDS_PAGE_SIZE |
SAP Sybase Error Number | 2789 |
SQL State | WW083 |
SQL Code | -1117L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 1118 | "Cannot change the MobiLink remote ID when the status of the last upload is unknown" |
|---|---|
Constant | CANNOT_CHANGE_ML_REMOTE_ID |
SAP Sybase Error Number | 2790 |
SQL State | 0AW17 |
SQL Code | -1118L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The MobiLink server uses the remote ID to track synchronization progress. If the status of the previous upload is unknown then you must resolve this condition before changing the remote ID. |