Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1611 | "Unable to copy file %1" |
|---|---|
Constant | UNABLE_TO_COPY_FILE |
SAP Sybase Error Number | 3253 |
SQL State | 08WB7 |
SQL Code | -1611L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The file name of the file to be copied |
Probable Cause | The request to copy a file failed |
| Error 1612 | "Cannot ALTER LDAP SERVER '%1' while ldap server is in active state." |
|---|---|
Constant | LDAPSERVER_IS_ACTIVE |
SAP Sybase Error Number | 3254 |
SQL State | WW215 |
SQL Code | -1612L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The LDAP SERVER name. |
Probable Cause | When an LDAP server is active, an ALTER statement may not change the ldap server options without also specifying WITH SUSPEND clause to also put the server in suspended state. This is an invalid LDAP server state change. |
| Error 1613 | "Tag ID: '%1' specifies a value not bounded by an array" |
|---|---|
Constant | FOR_JSON_EXPLICIT_NOT_IN_ARRAY |
SAP Sybase Error Number | 3255 |
SQL State | WX017 |
SQL Code | -1613L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The value of the tag ID which is not bounded by an array. |
Probable Cause | A union of multiple queries whose tags have the same parent may generate this error when the queries mix object and value notation. |
| Error 1614 | "Logical Server '%1' is used in both add and drop clauses" |
|---|---|
Constant | LS_IN_ADD_DROP |
SAP Sybase Error Number | 3256 |
SQL State | WQ023 |
SQL Code | -1614L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the logical server. |
Probable Cause | A logical Server appears in both the add and drop clauses of an alter logical server statement |
| Error 1615 | "LS Policy '%1' cannot be dropped because this policy is currently being used by a logical server" |
|---|---|
Constant | LSP_IN_USE_BY_LS |
SAP Sybase Error Number | 3257 |
SQL State | WQ024 |
SQL Code | -1615L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | LS policy name. |
Probable Cause | A logical server policy cannot be dropped if a logical server is using it. |
| Error 1616 | "'%1' being used incorrectly in ls policy statement" |
|---|---|
Constant | LSP_USING_INCORRECT_ARGS |
SAP Sybase Error Number | 3258 |
SQL State | WQ025 |
SQL Code | -1616L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | LS policy option name. |
Probable Cause | A clause in a ls policy sql statement has been used incorrectly. |
| Error 1617 | "The %1 remote data access class is no longer supported, please use %2 instead" |
|---|---|
Constant | OMNI_JDBC_NO_LONGER_SUPPORTED |
SAP Sybase Error Number | 3259 |
SQL State | WO033 |
SQL Code | -1617L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The JDBC based remote data access class. |
Parameter 2 | The preferred ODBC based remote data access class. |
Probable Cause | You attempted to use a JDBC based remote data access class which is no longer supported. Please use the appropriate ODBC based class instead. |
| Error 1618 | "The %1 remote data access class has been deprecated, please use %2 instead or change cis_option" |
|---|---|
Constant | OMNI_JDBC_DEPRECATED |
SAP Sybase Error Number | 3260 |
SQL State | WO034 |
SQL Code | -1618L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The JDBC based remote data access class. |
Parameter 2 | The preferred ODBC based remote data access class. |
Probable Cause | You attempted to use a JDBC based remote data access class which has been deprecated. Please use the appropriate ODBC based class instead; or change the cis_option setting to re-enable this feature. |
| Error 1619 | "logical server '%1' cannot be used in a connect string" |
|---|---|
Constant | LS_NOT_ALLOWED |
SAP Sybase Error Number | 3261 |
SQL State | WQ026 |
SQL Code | -1619L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | logical servername. |
Probable Cause | This logical server cannot be used as an argument to the connection string parameter logicalserver |
| Error 1620 | "The value specified is not within the required range %1 to %2." |
|---|---|
Constant | LDAPUA_OPT_OUT_OF_RANGE |
SAP Sybase Error Number | 3262 |
SQL State | WW217 |
SQL Code | -1620L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The minimum value for this option. |
Parameter 2 | The maximum value for this option. |
Probable Cause | The specified value for an LDAP server option is too big or too small. |
| Error 1621 | "LDAP server %1 may not accept anonymous binds." |
|---|---|
Constant | LDAPUA_ANONBINDERR |
SAP Sybase Error Number | 3263 |
SQL State | WW218 |
SQL Code | -1621L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The LDAP server name or search URL specifying the search. |
Probable Cause | An LDAPUA search or validate failed returning LDAP_INAPPROPRIATE_AUTH due to invalid settings for the target LDAP server. Check the access account values for the named LDAP server or search URL. |
| Error 1622 | "Bind to LDAP server %1 without a password is not allowed." |
|---|---|
Constant | LDAPUA_UTP |
SAP Sybase Error Number | 3264 |
SQL State | WW219 |
SQL Code | -1622L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The LDAP server name or search URL specifying the search. |
Probable Cause | An LDAPUA search or validate failed returning LDAP_UNWILLING_TO_PERFORM due to invalid settings for the target LDAP server. Check access account values for the named LDAP server or search URL. |
| Error 1623 | "The search on LDAP server %1 completed with no matching results." |
|---|---|
Constant | LDAPUA_NO_SEARCH_RESULTS |
SAP Sybase Error Number | 3265 |
SQL State | WW220 |
SQL Code | -1623L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The LDAP server name or search URL specifying the search. |
Probable Cause | An LDAPUA search or validate failed returning LDAP_NO_RESULTS_RETURNED. This error is expected when the user does not exist in the LDAP server. |
| Error 1624 | "The length of the value specified is too long, it exceeds the limit of %1 bytes." |
|---|---|
Constant | LDAPUA_OPT_TOO_LONG |
SAP Sybase Error Number | 3266 |
SQL State | WW216 |
SQL Code | -1624L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The maximum length of the value. |
Probable Cause | The specified value for an LDAP server option is too long. Specify a shorter string. |
| Error 1625 | "The UltraLite database deploy file is invalid (code: %1, file: %2)" |
|---|---|
Constant | ULTRALITE_DEPLOY_FILE_INVALID |
SAP Sybase Error Number | 3267 |
SQL State | WU002 |
SQL Code | -1625L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The diagnostic code. |
Parameter 2 | The associated filename, if applicable. |
Probable Cause | The UltraLite database deploy file is invalid. This can occur if the wrong file is deployed, or if the file is damaged. Diagnostic code 1 indicates the file is not a deploy file or has subsequently been corrupted. Diagnostic code 2 indicates the file is not a valid size. |
| Error 1626 | "The logical server policy for logical server '%1' does not allow 'redirect=yes' in the connection string" |
|---|---|
Constant | LS_POLICY_DOES_NOT_ALLOW_REDIRECTION |
SAP Sybase Error Number | 3268 |
SQL State | WQ027 |
SQL Code | -1626L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | logical servername. |
Probable Cause | This logical server policy for this logical server does not allow redirection" |
| Error 1627 | "TLS ON cannot be used with URL %1" |
|---|---|
Constant | LDAPUA_TLS_WITH_LDAPS |
SAP Sybase Error Number | 3269 |
SQL State | WW240 |
SQL Code | -1627L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The LDAP URL that is using Secure LDAP. |
Probable Cause | The LDAP server is specified with TLS ON and the specified LDAP URL uses Secure LDAP, that is, 'ldaps' instead of 'ldap', which is not a valid combination. Use either TLS ON or an 'ldaps' URL. |
| Error 1628 | "logical server '%1' cannot be used as a default logical server" |
|---|---|
Constant | LS_NOT_ALLOWED_AS_DEFAULT |
SAP Sybase Error Number | 3270 |
SQL State | WQ028 |
SQL Code | -1628L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | logical servername. |
Probable Cause | This logical server cannot be used as a default logical server |
| Error 1629 | "Only one IDENTIFIED BY value may be specified." |
|---|---|
Constant | LDAPUA_TOO_MANY_IDENTBY |
SAP Sybase Error Number | 3271 |
SQL State | WW241 |
SQL Code | -1629L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The LDAP server is specified with more than one password or is specified with both IDENTIED BY and IDENTIFIED BY ENCRYPTED. Set only one password. |
| Error 1630 | "Server '%1' is not allowed to have different values for ls policy option temp_data_in_shared_temp" |
|---|---|
Constant | LS_POLICY_OPTION_VALUE_DIFFERENT |
SAP Sybase Error Number | 3272 |
SQL State | WQ029 |
SQL Code | -1630L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | multiplex servername. |
Probable Cause | A server is not allowed to have different values for temp_data_in_shared_temp ls policy option |