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 |
|---|---|---|---|---|---|
| 3085 | Error | 2FW06 | -1415L | "Error parsing geometry internal serialization at offset %1" | There was an error parsing the internal serialization string. Click here for a list of possible parameters and odbc states. |
| 3087 | Error | 2FW08 | -1417L | "Error parsing well-known-binary (WKB): type code %1 at offset %2 is invalid" | The well-known binary string contains a type code that is not supported. Click here for a list of possible parameters and odbc states. |
| 3088 | Error | 2FW09 | -1418L | "Error parsing well-known-binary (WKB): type code %1 at offset %2 is not a valid subtype of the parent" | 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. Click here for a list of possible parameters and odbc states. |
| 3089 | Error | 2FW10 | -1419L | "Error parsing well-known-binary (WKB): unexpected end of input" | A well-known binary string was shorter than expected. Click here for a list of possible parameters and odbc states. |
| 3090 | Error | 2FW11 | -1420L | "Error parsing well-known-binary (WKB): inconsistent dimensions at offset %1" | 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. Click here for a list of possible parameters and odbc states. |
| 3091 | Error | 2FW12 | -1421L | "Error parsing well-known-binary (WKB): invalid byte order mark %1 at offset %2" | 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. Click here for a list of possible parameters and odbc states. |
| 3092 | Error | 2FW13 | -1422L | "Error parsing shapefile record" | The shapefile contains an invalid record. Click here for a list of possible parameters and odbc states. |
| 3093 | Error | 2FW14 | -1423L | "Error parsing shapefile attributes" | The shapefile contains invalid attributes. Click here for a list of possible parameters and odbc states. |
| 3094 | Error | 2FW15 | -1424L | "Invalid shapefile filename" | The specified shapefile filename is not valid. Click here for a list of possible parameters and odbc states. |
| 3095 | Error | 2FW16 | -1425L | "The multi patch shapefile shape is not supported" | The shapefile contains a multi patch object; this type is not supported. Click here for a list of possible parameters and odbc states. |
| 3096 | Error | 2FW19 | -1426L | "The embedded SRID (%1) conflicts with the provided SRID (%2)." | A call to a spatial method had a string with an embedded SRID that differed from the SRID parameter to the method. Click here for a list of possible parameters and odbc states. |
| 3097 | Error | 2FW20 | -1427L | "The embedded SRID are inconsistent (%1 and %2)." | A geometry in a string representation contains objects from different spatial reference systems. Click here for a list of possible parameters and odbc states. |
| 3098 | Error | 2FW21 | -1428L | "The format type '%1' is not recognized." | The specified format type is not recognized. Click here for a list of possible parameters and odbc states. |
| 3099 | Error | 2FW22 | -1429L | "The format type '%1' cannot be used here." | The specified format type cannot be used in this context. Click here for a list of possible parameters and odbc states. |
| 3100 | Error | 2FW23 | -1430L | "An input string in '%1' format cannot be used here." | A string with the specified format cannot be used in this context. Click here for a list of possible parameters and odbc states. |
| 3101 | Error | 2FW24 | -1431L | "The format specification syntax is invalid." | The format specification is invalid. Click here for a list of possible parameters and odbc states. |
| 3102 | Error | 2FW25 | -1432L | "The format specification option '%1' is not recognized." | The named option is not supported for the format specification. Click here for a list of possible parameters and odbc states. |
| 3103 | Error | 2FW26 | -1433L | "The value '%2' is not a valid setting for the '%1' format specification option." | The value is not accepted by the specification option. Click here for a list of possible parameters and odbc states. |
| 3104 | Error | 2FW27 | -1434L | "The data is not in a recognized format." | The provided string is not in a recognized format to parse a geometry. Click here for a list of possible parameters and odbc states. |
| 3105 | Error | 2FW28 | -1435L | "A geometry with SRID=%1 is not supported for method %2." | The named method does not support geometries in the specified spatial reference system. For example, the method might not support round-Earth data. Click here for a list of possible parameters and odbc states. |