Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2699 | Error | WW063 | -1030L | "Secure HTTP connections are not supported on this platform" | A Secure HTTP connection was attempted, but is not supported on this platform. Click here for a list of possible parameters and odbc states. |
| 2700 | Error | 42WB3 | -1031L | "Syntax error near '%1' -- Materialized view definition must not use the following construct: '%2'" | You attempted to create a materialized view whose definition violates one of the restrictions. Click here for a list of possible parameters and odbc states. |
| 2701 | Error | 42WB4 | -1032L | "Syntax error near '%1' -- The materialized view cannot be changed to immediate because its definition contains an illegal construct: '%2'" | You attempted to change the refresh type to immediate for a materialized view whose definition violates one of the restrictions. Click here for a list of possible parameters and odbc states. |
| 2702 | Error | 08W89 | -1033L | "Unable to start database server: Server fatal error" | The database server failed to start because a fatal error or assertion failure occurred. More information may be available in the Windows event log or Unix system log or by manually starting the database server. Click here for a list of possible parameters and odbc states. |
| 2703 | Error | WW064 | -1034L | "The '%1' attribute is not valid with procedure type '%2'" | This attribute is not applicable to the given procedure type. Click here for a list of possible parameters and odbc states. |
| 2704 | Error | WL008 | -1035L | "LOAD TABLE not permitted on mirrored database" | LOAD TABLE statements are not permitted when a database is being mirrored, since the file being loaded might not be accessible by the other server. Click here for a list of possible parameters and odbc states. |
| 2705 | Error | 08W90 | -1036L | "The DBN/DBF parameters do not match the database for this alternate server name" | The DBN or DBF parameters specified do not match the database using the specified alternate server name. Click here for a list of possible parameters and odbc states. |
| 2706 | Error | 55W16 | -1037L | "Cannot drop or modify object '%1' because at least one other object ( %2 '%3') depends upon it" | You attempted to drop or modify an object, such as a table or a column, that is used by another object, such as a materialized view, that cannot be automatically invalidated. The dependent object must be disabled or dropped before a drop or modification can be permitted. Click here for a list of possible parameters and odbc states. |
| 2707 | Error | 55W17 | -1038L | "Cannot use view '%1' because it has been disabled" | You attempted to reference a view that has been disabled. The view must be enabled before it can be used again. Click here for a list of possible parameters and odbc states. |
| 2708 | Error | 08W91 | -1039L | "Cannot connect to mirror server. Use server name '%1' to find the primary server" | You have attempted to connect to the mirror server in a mirroring system. You should change your connection string or DSN to use the server name for the mirroring system. Click here for a list of possible parameters and odbc states. |
| 2709 | Error | 55W18 | -1040L | "Cannot use view '%1' because it is invalid" | You attempted to reference an invalid view. The view must be enabled before it can be used again. Click here for a list of possible parameters and odbc states. |
| 2710 | Error | 42WB5 | -1041L | "Materialized View '%1' not found" | You misspelled the name of a materialized view, or you did not qualify a materialized view name with a user name. For example, you might have referred to "Employees" instead of "DBA"."Employees". Click here for a list of possible parameters and odbc states. |
| 2711 | Error | WW065 | -1042L | "Cannot add a comment to a table declared as LOCAL TEMPORARY" | You attempted to add a comment to a table that has been declared as LOCAL TEMPORARY. This is not allowed. Click here for a list of possible parameters and odbc states. |
| 2712 | Error | 57W01 | -1043L | "Request interrupted due to timeout" | The current request was canceled during its execution since it ran for longer than the request_timeout database option value. The database was able to stop the operation without doing a rollback. If the statement is an INSERT, UPDATE, or DELETE, any changes made by the statement will be canceled. If the statement is a data definition statement (for example CREATE TABLE), the statement will be canceled, but the COMMIT that was done as a side effect will not be canceled. Click here for a list of possible parameters and odbc states. |
| 2713 | Error | 28W11 | -1044L | "Invalid password: %1" | The attempt to create a new user ID or change a password failed. The function specified by the verify_password_function option disallowed the password. Click here for a list of possible parameters and odbc states. |
| 2714 | Error | WB015 | -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. |
| 2715 | Error | 55W19 | -1046L | "Illegal column definition: %1" | You are attempting to define a column in a way that is not allowed. Click here for a list of possible parameters and odbc states. |
| 2716 | Error | 55W20 | -1047L | "This database does not support encrypted tables" | You tried to create an encrypted table in a database that does not support them. Click here for a list of possible parameters and odbc states. |
| 2717 | Error | WT028 | -1393L | "Error initializing external term breaker" | The external term breaker could not be initialized because of an internal error. Click here for a list of possible parameters and odbc states. |
| 2718 | Error | WT027 | -1396L | "Error initializing external prefilter" | The external prefilter could not be initialized because of an internal error. Click here for a list of possible parameters and odbc states. |