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 |
|---|---|---|---|---|---|
| 3147 | Error | 2FW70 | -1477L | "The SRID %1 does not identify a geographic spatial reference system" | The methods ST_Lat() and ST_Long() can only be used for geographic spatial reference systems. Click here for a list of possible parameters and odbc states. |
| 3148 | Error | 2FW71 | -1478L | "ST_Geometry arguments not supported by SQL function %1" | The specified SQL function does not support geometry parameters. Click here for a list of possible parameters and odbc states. |
| 3149 | Error | 2FW72 | -1479L | "An expression of type %1 is not union-compatible with type %2" | The two types cannot be combined, for example in a set operation such as UNION or in a SQL function such as COALESCE. Click here for a list of possible parameters and odbc states. |
| 3150 | Error | 2FW73 | -1480L | "An internal error has occurred in the spatial library" | An unexpected error occurred. Click here for a list of possible parameters and odbc states. |
| 3152 | Error | 2FW77 | -1482L | "Curve contains nearly antipodal points %1 and %2 (near '%3')" | A curve contains two points that are nearly antipodal. These define an ambiguous segment in a round-Earth spatial reference system. Click here for a list of possible parameters and odbc states. |
| 3153 | Error | 2FW78 | -1483L | "LineString must contain at least 2 points (near '%1')" | The linestring contains only a single point. Click here for a list of possible parameters and odbc states. |
| 3154 | Error | 2FW79 | -1484L | "Value %1 out of range for coordinate %2 (SRS bounds [%3, %4] exceeded by more than 50%)" | The geometry contains a point outside of the bounds specified by the spatial reference system. Click here for a list of possible parameters and odbc states. |
| 3155 | Error | 2FW80 | -1485L | "Invalid polygon: ring is not closed (near '%1')" | One of the provided curves is not a closed ring. Click here for a list of possible parameters and odbc states. |
| 3156 | Error | 2FW81 | -1486L | "Invalid polygon: ring has zero area (near '%1')" | One of the provided rings has zero area and cannot be a valid polygon ring. Click here for a list of possible parameters and odbc states. |
| 3157 | Error | 2FW82 | -1487L | "Invalid polygon: curve is not a ring" | One of the curves is not a ring and cannot be used to form a polygon. Click here for a list of possible parameters and odbc states. |
| 3158 | Error | 2FW83 | -1488L | "Invalid polygon: ring is larger than allowed for SRID=%1 (near '%2')" | One of the rings is larger than the specified spatial reference system supports. Click here for a list of possible parameters and odbc states. |
| 3159 | Error | 01F01 | -1489L | "Position %1 is invalid (should be between %2 and %3)" | The provided position is not valid. It should be between the specified minimum and maximum. Click here for a list of possible parameters and odbc states. |
| 3160 | Error | 01FW1 | -1490L | "Polygon ring order has been reoriented" | The rings of a polygon were automatically reoriented on input. This is a notification only. Click here for a list of possible parameters and odbc states. |
| 3161 | Error | 01FW2 | -1491L | "CircularString with 3 points has been converted to use 5 points" | A curve containing a CircularString with a 3-point circle has been converted to use a 5-point circle. This is a notification only. Click here for a list of possible parameters and odbc states. |
| 3162 | Error | 2FW84 | -1494L | "Geometries with CircularString not supported (near \"%1\")" | The method or operation does not support geometries with CircularString elements. Click here for a list of possible parameters and odbc states. |
| 3163 | Error | 2FW85 | -1495L | "Geometries with CircularString are not supported in spatial reference system %1" | The method does not support geometries with CircularString elements. Click here for a list of possible parameters and odbc states. |
| 3164 | Error | WL017 | -1496L | "LOAD TABLE error: Invalid content encountered on row %1 of the data file" | The LOAD TABLE statement failed because a scanning error occurred on the indicated line of the data file specified in the statement. This error can occur if a line is truncated or if delimiters are missing. Click here for a list of possible parameters and odbc states. |
| 3165 | Error | 28W17 | -1497L | "The synchronization failed because MobiLink returned authentication status '%1' with value '%2'" | MobiLink returned an authentication status to the remote database indicating failure. The status and value numbers indicate why the authentication failed. For example, the password was invalid, or a synchronization is already in progress for this remote. Click here for a list of possible parameters and odbc states. |
| 3166 | Error | WU001 | -1498L | "'%1' is an unknown property" | The specified property is unknown. Click here for a list of possible parameters and odbc states. |
| 3167 | Error | 2FW86 | -1499L | "Invalid grid size %1" | The specified grid size cannot be used with the spatial reference system. The grid size must be selected based on the bounds of space. Click here for a list of possible parameters and odbc states. |