Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1407 | "Error parsing well-known-binary (WKB) at offset %1" |
|---|---|
Constant | SLERR_WKB_PARSE |
SAP Sybase Error Number | 3077 |
SQL State | 2FF23 |
SQL Code | -1407L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The byte offset within the binary string where the error was detected. |
Probable Cause | An error was detected while parsing the well-known binary of a geometry. |
| Error 1408 | "Mixed coordinate dimensions" |
|---|---|
Constant | SLERR_MIXED_DIM |
SAP Sybase Error Number | 3078 |
SQL State | 2FF25 |
SQL Code | -1408L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The method contains geometries that have a mixture of coordinate dimensions (Z and M values). |
| Error 1409 | "Unknown spatial reference system (%1)" |
|---|---|
Constant | SLERR_SRID_UNKNOWN |
SAP Sybase Error Number | 3079 |
SQL State | 2FF59 |
SQL Code | -1409L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The spatial reference system identifier. |
Probable Cause | The provided SRID does not match a defined spatial reference system. |
| Error 1410 | "An ST_CircularString cannot be constructed from %1 points (near '%2')" |
|---|---|
Constant | SLERR_CIRC_NUM_POINTS |
SAP Sybase Error Number | 3080 |
SQL State | 2FF71 |
SQL Code | -1410L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The incorrect number of points given. |
Parameter 2 | The value or method where the error was detected. |
Probable Cause | A circularstring geometry should consist of three points followed optionally by an arbitrary number of pairs of points. |
| Error 1411 | "Cannot convert from %1 to %2 (near %3)." |
|---|---|
Constant | SLERR_ST_TO_XXX_FAILN |
SAP Sybase Error Number | 3081 |
SQL State | 2FF16 |
SQL Code | -1411L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The geometry type of the value. |
Parameter 2 | The geometry type of the target. |
Parameter 3 | The value or method where the error was detected. |
Probable Cause | The value could not be converted to the specified target type. |
| Error 1412 | "Support for spatial is not available for this database" |
|---|---|
Constant | SLERR_NEED_UPGRADE |
SAP Sybase Error Number | 3082 |
SQL State | 2FW02 |
SQL Code | -1412L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Operations involving spatial support cannot be used with this database because it needs to be upgraded to use spatial features. |
| Error 1413 | "Spatial feature %1 is not supported" |
|---|---|
Constant | SLERR_NYI |
SAP Sybase Error Number | 3083 |
SQL State | 2FW03 |
SQL Code | -1413L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the unsupported feature. |
Probable Cause | The specified feature is not supported. |
| Error 1414 | "Error parsing well-known-text (WKT): inconsistent dimensions at offset %1" |
|---|---|
Constant | SLERR_WKT_PARSE_INCONSISTENT_ZM |
SAP Sybase Error Number | 3084 |
SQL State | 2FW05 |
SQL Code | -1414L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The offset within the well-known text string where the error was detected. |
Probable Cause | There was a mixture of coordinate dimensions detected at the specified offset. For example, one geometry in a collection might have a Z value while another doesn't. |
| Error 1415 | "Error parsing geometry internal serialization at offset %1" |
|---|---|
Constant | SLERR_SERIAL_PARSE |
SAP Sybase Error Number | 3085 |
SQL State | 2FW06 |
SQL Code | -1415L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The byte offset within the internal serialization. |
Probable Cause | There was an error parsing the internal serialization string. |
| Error 1417 | "Error parsing well-known-binary (WKB): type code %1 at offset %2 is invalid" |
|---|---|
Constant | SLERR_WKB_PARSE_TYPE |
SAP Sybase Error Number | 3087 |
SQL State | 2FW08 |
SQL Code | -1417L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The unsupported type code value. |
Parameter 2 | The byte offset within the binary string where the error was detected. |
Probable Cause | The well-known binary string contains a type code that is not supported. |
| Error 1418 | "Error parsing well-known-binary (WKB): type code %1 at offset %2 is not a valid subtype of the parent" |
|---|---|
Constant | SLERR_WKB_PARSE_TYPE_NOT_PERMITTED |
SAP Sybase Error Number | 3088 |
SQL State | 2FW09 |
SQL Code | -1418L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The unsupported type code value. |
Parameter 2 | The byte offset within the binary string where the error was detected. |
Probable Cause | The well-known binary string contains a child geometry within a parent geometry and the child is not one of the types allowed by the parent. |
| Error 1419 | "Error parsing well-known-binary (WKB): unexpected end of input" |
|---|---|
Constant | SLERR_WKB_PARSE_UNEXPECTED_EOF |
SAP Sybase Error Number | 3089 |
SQL State | 2FW10 |
SQL Code | -1419L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A well-known binary string was shorter than expected. |
| Error 1420 | "Error parsing well-known-binary (WKB): inconsistent dimensions at offset %1" |
|---|---|
Constant | SLERR_WKB_PARSE_INCONSISTENT_ZM |
SAP Sybase Error Number | 3090 |
SQL State | 2FW11 |
SQL Code | -1420L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The byte offset within the binary string where the error was detected. |
Probable Cause | The well-known binary string contains geometries with different numbers of coordinate dimensions. For example, it could contain a point with a Z value and another without a Z value. |
| Error 1421 | "Error parsing well-known-binary (WKB): invalid byte order mark %1 at offset %2" |
|---|---|
Constant | SLERR_WKB_PARSE_INVALID_BOM |
SAP Sybase Error Number | 3091 |
SQL State | 2FW12 |
SQL Code | -1421L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The value of the byte-order mark. |
Parameter 2 | The byte offset within the binary string where the error was detected. |
Probable Cause | The well-known binary string has an invalid byte order mark. This could happen if a binary string that is not in the well-known binary format is used. |
| Error 1422 | "Error parsing shapefile record" |
|---|---|
Constant | SLERR_SHAPE_PARSE |
SAP Sybase Error Number | 3092 |
SQL State | 2FW13 |
SQL Code | -1422L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The shapefile contains an invalid record. |
| Error 1423 | "Error parsing shapefile attributes" |
|---|---|
Constant | SLERR_SHAPE_PARSE_ATTRIBUTES |
SAP Sybase Error Number | 3093 |
SQL State | 2FW14 |
SQL Code | -1423L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The shapefile contains invalid attributes. |
| Error 1424 | "Invalid shapefile filename" |
|---|---|
Constant | SLERR_SHAPE_INVALID_FILENAME |
SAP Sybase Error Number | 3094 |
SQL State | 2FW15 |
SQL Code | -1424L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The specified shapefile filename is not valid. |
| Error 1425 | "The multi patch shapefile shape is not supported" |
|---|---|
Constant | SLERR_SHAPE_MULTIPATCH |
SAP Sybase Error Number | 3095 |
SQL State | 2FW16 |
SQL Code | -1425L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The shapefile contains a multi patch object; this type is not supported. |
| Error 1426 | "The embedded SRID (%1) conflicts with the provided SRID (%2)." |
|---|---|
Constant | SLERR_SRID_CONFLICT_EMBED_PARAM |
SAP Sybase Error Number | 3096 |
SQL State | 2FW19 |
SQL Code | -1426L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The SRID within the parsed string. |
Parameter 2 | The SRID provided as a parameter. |
Probable Cause | A call to a spatial method had a string with an embedded SRID that differed from the SRID parameter to the method. |
| Error 1427 | "The embedded SRID are inconsistent (%1 and %2)." |
|---|---|
Constant | SLERR_SRID_CONFLICT_EMBED_EMBED |
SAP Sybase Error Number | 3097 |
SQL State | 2FW20 |
SQL Code | -1427L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The first SRID. |
Parameter 2 | The second SRID. |
Probable Cause | A geometry in a string representation contains objects from different spatial reference systems. |