Messages 1095 through 1115

Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL Code Msg Type Number SQL State Message Possible Cause
-1095L Error 2765 WW071 "The specified HTTP header contains illegal or non-ASCII characters" HTTP headers must contain printable ASCII characters.

Click here for a list of possible parameters and odbc states.

-1096L Error 2766 WW072 "The specified HTTP header is malformed" The HTTP header is missing the colon delimiter or a folding construct is malformed.

Click here for a list of possible parameters and odbc states.

-1097L Error 2767 08W95 "ATTACH TRACING could not connect to the tracing database" A connection to the tracing database could not be established. Check your connection string and verify that other clients can connect. Note that if you are trying to attach tracing to another server, perhaps the connection is being blocked by a firewall.

Click here for a list of possible parameters and odbc states.

-1098L Error 2768 08W96 "A tracing connection is already active" 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.

Click here for a list of possible parameters and odbc states.

-1099L Error 2769 55W25 "Transact-SQL outer joins are currently disabled" 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.

Click here for a list of possible parameters and odbc states.

-1100L Error 2771 WW045 "The operation failed because column '%1''s type does not support streaming" 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.

Click here for a list of possible parameters and odbc states.

-1101L Error 2772 WW073 "Column '%1' not part of any indexes in its containing table" The specified column is not part of any indexes belonging to the containing table.

Click here for a list of possible parameters and odbc states.

-1102L Error 2773 WW074 "Unable to retry download because upload is not finished" The MobiLink server could not restart the download because the MobiLink server has not received the entire upload stream.

Click here for a list of possible parameters and odbc states.

-1103L Error 2774 WW075 "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.

-1104L Error 2775 54W10 "Too many users in database" 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.

Click here for a list of possible parameters and odbc states.

-1106L Error 2777 WW077 "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.

-1107L Error 2778 54W11 "Too many references to a BLOB" 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.

Click here for a list of possible parameters and odbc states.

-1108L Error 2779 WW078 "Unable to access the file system on the device" On a Palm device, you have tried to utilize the VFS file system, but that feature has not been enabled on the device.

Click here for a list of possible parameters and odbc states.

-1109L Error 2780 WW079 "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 database that uses keyless encryption (obfuscation for example).

Click here for a list of possible parameters and odbc states.

-1110L Error 2781 WW080 "UltraLite cannot synchronize because a synchronization is already running" 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.

Click here for a list of possible parameters and odbc states.

-1111L Error 2782 WW081 "Information for synchronization was not provided" You must supply information for synchronization in the synchronization call.

Click here for a list of possible parameters and odbc states.

-1112L Error 2783 WW082 "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.

-1113L Error 2784 42WBF "Correlation name '%1' is not valid for use with the ROWID function" 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.

Click here for a list of possible parameters and odbc states.

-1114L Error 2785 42W86 "Invalid setting for SOAP header '%1'" You supplied an invalid value for a SOAP header.

Click here for a list of possible parameters and odbc states.

-1115L Error 2786 42WC1 "Table '%1' contains an invalid reference to the ROWID function" The ROWID function cannot be used in a computed column expression or in a CHECK constraint.

Click here for a list of possible parameters and odbc states.


Created November 10, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com