Platform error codes

Error codes are defined here as integers and organized into groups based on category of service. We do our best to never change a defined error code once the API is officially released, but we reserve the right to make changes. Error codes are documented here for reference. Please consult the release notes regarding any changes to these values.

There are distinct classes of errors, depending on the service invoked. As the architecture dictates, errors may originate from the API, the runtime core supporting the API, or the service (the servers the API connects to implementing certain services.) Check the error domain if this is information useful to your app. In most cases you only need the error code to determine the cause of the error and possible remedy.

Runtime errors

Internal runtime errors are thrown by the core library when things go wrong client-side. Where possible the details of the exception are described. In many instances, the details of the exception are dependent on the context that generated the exception. In these cases, refer to the specific API that generated the error for more information.

Error code	Description
-1	Unknown error. (since 100.0.0)
0	Success. (since 100.0.0)
1	A null pointer. (since 100.0.0)
2	Invalid argument. (since 100.0.0)
3	Not implemented. (since 100.0.0)
4	Out of range. (since 100.0.0)
5	Invalid access. (since 100.0.0)
6	Illegal state. (since 100.0.0)
7	Not found. (since 100.0.0)
8	Entity exists. (since 100.0.0)
9	Timeout. (since 100.0.0)
10	Regular expression error. (since 100.0.0)
11	Property not supported. (since 100.0.0)
12	No permission. (since 100.0.0)
13	File error. (since 100.0.0)
14	File not found. (since 100.0.0)
15	Invalid call. (since 100.0.0)
16	IO error. (since 100.0.0)
17	User canceled. (since 100.0.0)
18	Internal error. (since 100.0.0)
19	Conversion failed. (since 100.0.0)
20	No data. (since 100.0.0)
21	Invalid JSON. (since 100.0.0)
22	Propagated error. (since 100.0.0)
23	Invalid XML. (since 100.1.0)
24	Object is already owned. (since 100.1.0)
25	Reserved for use by Qt. (since 100.5.0)
26	The resource is past its expiry date. (since 100.5.0)
27	Nullability violation. (since 100.8.0)
28	Invalid property. (since 100.12.0)

SQL errors

Internal errors related to the SQL storage engine.

Error code	Description
1001	SQLite error. (since 100.0.0)
1002	SQLite internal error. (since 100.0.0)
1003	SQLite permission. (since 100.0.0)
1004	SQLite operation aborted. (since 100.0.0)
1005	SQLite database busy. (since 100.0.0)
1006	SQLite database locked. (since 100.0.0)
1007	SQLite out of memory. (since 100.0.0)
1008	SQLite read only. (since 100.0.0)
1009	SQLite operation interrupted. (since 100.0.0)
1010	SQLite IO error. (since 100.0.0)
1011	SQLite corrupt database. (since 100.0.0)
1012	SQLite not found. (since 100.0.0)
1013	SQLite disk full. (since 100.0.0)
1014	SQLite cannot open. (since 100.0.0)
1015	SQLite file locking protocol. (since 100.0.0)
1016	SQLite empty error. (since 100.0.0)
1017	SQLite schema changed. (since 100.0.0)
1018	SQLite string or data blob too large. (since 100.0.0)
1019	SQLite constraint violation. (since 100.0.0)
1020	SQLite data type mismatch. (since 100.0.0)
1021	SQLite interface misuse. (since 100.0.0)
1022	SQLite no large file support. (since 100.0.0)
1023	SQLite statement not authorized. (since 100.0.0)
1024	SQLite format error. (since 100.0.0)
1025	SQLite out of range. (since 100.0.0)
1026	Not an SQLite database. (since 100.0.0)
1027	SQLite unusual operation notice. (since 100.0.0)
1028	SQLite unusual operation warning. (since 100.0.0)
1029	SQLite row is available. (since 100.0.0)
1030	SQLite operation is complete. (since 100.0.0)

Geometry errors

Internal errors related to the geometry engine.

Error code	Description
2000	Unknown geometry error. (since 100.1.0)
2001	Corrupt geometry. (since 100.0.0)
2002	Empty geometry. (since 100.0.0)
2003	Math singularity. (since 100.0.0)
2004	Geometry buffer too small. (since 100.0.0)
2005	Geometry invalid shape type. (since 100.0.0)
2006	Geometry projection out of supported range. (since 100.0.0)
2007	Non simple geometry. (since 100.0.0)
2008	Cannot calculate geodesic. (since 100.0.0)
2009	Geometry notation conversion. (since 100.0.0)
2010	Missing grid file. (since 100.0.0)

Geodatabase errors

Internal errors related to geodatabase queries.

Error code	Description
3001	Geodatabase value out of range. (since 100.0.0)
3002	Geodatabase data type mismatch. (since 100.0.0)
3003	Geodatabase invalid XML. (since 100.0.0)
3004	Database already exists. (since 100.0.0)
3005	Database does not exist. (since 100.0.0)
3006	Geodatabase name longer than 128 characters. (since 100.0.0)
3007	Geodatabase invalid shape type. (since 100.0.0)
3008	Geodatabase raster not supported. (since 100.0.0)
3009	Geodatabase relationship class one to one. (since 100.0.0)
3010	Geodatabase item not found. (since 100.0.0)
3011	Geodatabase duplicate code. (since 100.0.0)
3012	Geodatabase missing code. (since 100.0.0)
3013	Geodatabase wrong item type. (since 100.0.0)
3014	Geodatabase Id field not nullable. (since 100.0.0)
3015	Geodatabase default value not supported. (since 100.0.0)
3016	Geodatabase table not editable. (since 100.0.0)
3017	Geodatabase field not found. (since 100.0.0)
3018	Geodatabase field exists. (since 100.0.0)
3019	Geodatabase cannot alter field type. (since 100.0.0)
3020	Geodatabase cannot alter field width. (since 100.0.0)
3021	Geodatabase cannot alter field to nullable. (since 100.0.0)
3022	Geodatabase cannot alter field to editable. (since 100.0.0)
3023	Geodatabase cannot alter field to deletable. (since 100.0.0)
3024	Geodatabase cannot alter geometry properties. (since 100.0.0)
3025	Geodatabase unnamed table. (since 100.0.0)
3026	Geodatabase invalid type for domain. (since 100.0.0)
3027	Geodatabase min max reversed. (since 100.0.0)
3028	Geodatabase field not supported on relationship class. (since 100.0.0)
3029	Geodatabase relationship class key. (since 100.0.0)
3030	Geodatabase value is null. (since 100.0.0)
3031	Geodatabase multiple SQL statements. (since 100.0.0)
3032	Geodatabase no SQL statements. (since 100.0.0)
3033	Geodatabase geometry field missing. (since 100.0.0)
3034	Geodatabase transaction started. (since 100.0.0)
3035	Geodatabase transaction not started. (since 100.0.0)
3036	Geodatabase shape requires z. (since 100.0.0)
3037	Geodatabase shape requires m. (since 100.0.0)
3038	Geodatabase shape no z. (since 100.0.0)
3039	Geodatabase shape no m. (since 100.0.0)
3040	Geodatabase shape wrong type. (since 100.0.0)
3041	Geodatabase cannot update field type. (since 100.0.0)
3042	Geodatabase no rows affected. (since 100.0.0)
3043	Geodatabase subtype invalid. (since 100.0.0)
3044	Geodatabase subtype must be integer. (since 100.0.0)
3045	Geodatabase subtypes not enabled. (since 100.0.0)
3046	Geodatabase subtype exists. (since 100.0.0)
3047	Geodatabase duplicate field not allowed. (since 100.0.0)
3048	Geodatabase cannot delete field. (since 100.0.0)
3049	Geodatabase index exists. (since 100.0.0)
3050	Geodatabase index not found. (since 100.0.0)
3051	Geodatabase cursor not on row. (since 100.0.0)
3052	Geodatabase internal error. (since 100.0.0)
3053	Geodatabase cannot write geodatabase managed fields. (since 100.0.0)
3054	Geodatabase item already exists. (since 100.0.0)
3055	Geodatabase invalid spatial index name. (since 100.0.0)
3056	Geodatabase requires spatial index. (since 100.0.0)
3057	Geodatabase reserved name. (since 100.0.0)
3058	Geodatabase cannot update schema if change tracking. (since 100.0.0)
3059	Geodatabase invalid date. (since 100.0.0)
3060	Geodatabase database does not have changes. (since 100.0.0)
3061	Geodatabase replica does not exist. (since 100.0.0)
3062	Geodatabase storage type not supported. (since 100.0.0)
3063	Geodatabase replica model error. (since 100.0.0)
3064	Geodatabase replica client generation error. (since 100.0.0)
3065	Geodatabase replica no upload to acknowledge. (since 100.0.0)
3066	Geodatabase last write time in the future. (since 100.0.0)
3067	Geodatabase invalid argument. (since 100.0.0)
3068	Geodatabase transportation network corrupt. (since 100.0.0)
3069	Geodatabase transportation network file IO error. (since 100.0.0)
3070	Geodatabase feature has pending edits. (since 100.0.0)
3071	Geodatabase change tracking not enabled. (since 100.0.0)
3072	Geodatabase transportation network file open. (since 100.0.0)
3073	Geodatabase transportation network unsupported. (since 100.0.0)
3074	Geodatabase cannot sync copy. (since 100.0.0)
3075	Geodatabase access control denied. (since 100.0.0)
3076	Geodatabase geometry outside replica extent. (since 100.0.0)
3077	Geodatabase upload already in progress. (since 100.0.0)
3078	Geodatabase is closed. (since 100.5.0)
3079	Domain exists. (since 100.1.0)
3080	Geodatabase geometry type not supported. (since 100.5.0)
3081	ArcGISFeatureTable requires a global Id field to support adding bulk attachments. (since 100.9.0)
3082	Violated attribute constraint rule. (since 100.14.0)
3083	The evaluation of attribute rules is cyclic or exceeds maximum cascading level. (since 100.14.0)
3084	The client version required by the geodatabase is not yet supported. (since 200.2.0)

Geocode errors

Internal errors related to geocoding, address, and reverse address lookup.

Error code	Description
4001	Geocode unsupported file format. (since 100.0.0)
4002	Geocode unsupported spatial reference. (since 100.0.0)
4003	Geocode unsupported projection transformation. (since 100.0.0)
4004	Geocoder creation error. (since 100.0.0)
4005	Geocode intersections not supported. (since 100.0.0)
4006	Uninitialized geocode task. (since 100.0.0)
4007	Invalid geocode locator properties. (since 100.0.0)
4008	Geocode required field missing. (since 100.0.0)
4009	Geocode cannot read address. (since 100.0.0)
4010	Geocoding not supported. (since 100.0.0)
4011	Geocode geometry type not supported. (since 100.10.0)
4012	Geocode suggest address not supported. (since 100.10.0)
4013	Geocode suggest result corrupt. (since 100.10.0)

Network Analyst errors

Internal errors related to Network Analyst and routing tasks.

Error code	Description
5001	Network analyst invalid route settings. (since 100.0.0)
5002	Network analyst no solution. (since 100.0.0)
5003	Network analyst task canceled. (since 100.0.0)
5004	Network analyst invalid network. (since 100.0.0)
5005	Network analyst directions error. (since 100.0.0)
5006	Network analyst insufficient number of stops. (since 100.0.0)
5007	Network analyst stop unlocated. (since 100.0.0)
5008	Network analyst stop located on non traversable element. (since 100.0.0)
5009	Network analyst point barrier invalid added cost attribute name. (since 100.0.0)
5010	Network analyst line barrier invalid scaled cost attribute name. (since 100.0.0)
5011	Network analyst polygon barrier invalid scaled cost attribute name. (since 100.0.0)
5012	Network analyst polygon barrier invalid scaled cost attribute value. (since 100.0.0)
5013	Network analyst polyline barrier invalid scaled cost attribute value. (since 100.0.0)
5014	Network analyst invalid impedance attribute. (since 100.0.0)
5015	Network analyst invalid restriction attribute. (since 100.0.0)
5016	Network analyst invalid accumulate attribute. (since 100.0.0)
5017	Network analyst invalid directions time attribute. (since 100.0.0)
5018	Network analyst invalid directions distance attribute. (since 100.0.0)
5019	Network analyst invalid attribute parameters attribute name. (since 100.0.0)
5020	Network analyst invalid attributes parameters parameter name. (since 100.0.0)
5021	Network analyst invalid attributes parameters value type. (since 100.0.0)
5022	Network analyst invalid attribute parameters restriction usage value. (since 100.0.0)
5023	Network analyst network has no hierarchy attribute. (since 100.0.0)
5024	Network analyst no path found between stops. (since 100.0.0)
5025	Network analyst undefined input spatial reference. (since 100.0.0)
5026	Network analyst undefined output spatial reference. (since 100.0.0)
5027	Network analyst invalid directions style. (since 100.0.0)
5028	Deprecated. Network analyst invalid directions language. (since 100.0.0)
5029	Network analyst directions time and impedance attribute mismatch. (since 100.0.0)
5030	Network analyst invalid directions road class attribute. (since 100.0.0)
5031	Network analyst stop cannot be reached. (since 100.0.0)
5032	Network analyst stop time window starts before unix epoch. (since 100.0.0)
5033	Network analyst stop time window is inverted. (since 100.0.0)
5034	Walking mode route too large. (since 100.0.0)
5035	Stop has null geometry. (since 100.0.0)
5036	Point barrier has null geometry. (since 100.0.0)
5037	Polyline barrier has null geometry. (since 100.0.0)
5038	Polygon barrier has null geometry. (since 100.0.0)
5039	Online route task does not support search_where_clause condition. (since 100.0.0)
5040	Network analyst insufficient number of facilities. (since 100.0.0)
5041	Network analyst facility has null geometry. (since 100.0.0)
5042	Network analyst facility has invalid added cost attribute name. (since 100.0.0)
5043	Network analyst facility has negative added cost attribute. (since 100.0.0)
5044	Network analyst facility has invalid impedance cutoff. (since 100.0.0)
5045	Network analyst insufficient number of incidents. (since 100.0.0)
5046	Network analyst incident has null geometry. (since 100.0.0)
5047	Network analyst incident has invalid added cost attribute name. (since 100.0.0)
5048	Network analyst incident has negative added cost attribute. (since 100.0.0)
5049	Network analyst invalid target facility count. (since 100.0.0)
5050	Network analyst incident has invalid impedance cutoff. (since 100.0.0)
5051	Network analyst start time is before Unix epoch. (since 100.0.0)
5052	Network analyst invalid default impedance cutoff. (since 100.0.0)
5053	Network analyst invalid default target facility count. (since 100.0.0)
5054	Network analyst invalid polygon buffer distance. (since 100.0.0)
5055	Network analyst polylines cannot be returned. (since 100.0.0)
5056	Network analyst solving non time impedance, but time windows applied. (since 100.0.0)
5057	One or more stops have unsupported type. (since 100.1.0)
5058	Network analyst route starts or ends on a waypoint. (since 100.1.0)
5059	Network analyst reordering stops (Traveling Salesman Problem) is not supported when the collection of stops contains waypoints or rest breaks. (since 100.1.0)
5060	Network analyst waypoint contains time windows. (since 100.1.0)
5061	Network analyst waypoint contains added cost attribute. (since 100.1.0)
5062	Network analyst stop has unknown curb approach. (since 100.1.0)
5063	Network analyst point barrier has unknown curb approach. (since 100.1.0)
5064	Network analyst facility has unknown curb approach. (since 100.1.0)
5065	Network analyst incident has unknown curb approach. (since 100.1.0)
5066	Network dataset has no directions attributes. (since 100.3.0)
5067	Desired direction language not supported by platform. (since 100.3.0)
5068	Route result requires re-solving with current route task. (since 100.6.0)
5069	Input route result does not have directions. (since 100.6.0)
5070	Input route result does not have stops. (since 100.6.0)
5071	Input route result doesn't have the route with passed route index. (since 100.6.0)
5072	Input remaining destinations count doesn't match with input routes stops collection. (since 100.6.0)

JSON parsing errors

Errors that may occur when dealing with JSON.

Error code	Description
6001	JSON parser invalid token. (since 100.0.0)
6002	JSON parser invalid character. (since 100.0.0)
6003	JSON parser invalid unicode. (since 100.0.0)
6004	JSON parser invalid start of JSON. (since 100.0.0)
6005	JSON parser invalid end of pair. (since 100.0.0)
6006	JSON parser invalid end of element. (since 100.0.0)
6007	JSON parser invalid escape sequence. (since 100.0.0)
6008	JSON parser invalid end of field name. (since 100.0.0)
6009	JSON parser invalid start of field name. (since 100.0.0)
6010	JSON parser invalid start of comment. (since 100.0.0)
6011	JSON parser invalid decimal digit. (since 100.0.0)
6012	JSON parser invalid hex digit. (since 100.0.0)
6013	JSON parser expecting null. (since 100.0.0)
6014	JSON parser expecting true. (since 100.0.0)
6015	JSON parser expecting false. (since 100.0.0)
6016	JSON parser expecting closing quote. (since 100.0.0)
6017	JSON parser expecting not a number. (since 100.0.0)
6018	JSON parser expecting end of comment. (since 100.0.0)
6019	JSON parser unexpected end of data. (since 100.0.0)
6020	JSON object expecting start object. (since 100.0.0)
6021	JSON object expecting start array. (since 100.0.0)
6022	JSON object expecting value object. (since 100.0.0)
6023	JSON object expecting value array. (since 100.0.0)
6024	JSON object expecting value int32. (since 100.0.0)
6025	JSON object expecting integer type. (since 100.0.0)
6026	JSON object expecting number type. (since 100.0.0)
6027	JSON object expecting value string. (since 100.0.0)
6028	JSON object expecting value bool. (since 100.0.0)
6029	JSON object iterator not started. (since 100.0.0)
6030	JSON object iterator is finished. (since 100.0.0)
6031	JSON object key not found. (since 100.0.0)
6032	JSON object index out of range. (since 100.0.0)
6033	JSON string writer JSON is complete. (since 100.0.0)
6034	JSON string writer invalid JSON input. (since 100.0.0)
6035	JSON string writer expecting container. (since 100.0.0)
6036	JSON string writer expecting key or end object. (since 100.0.0)
6037	JSON string writer expecting value or end array. (since 100.0.0)
6038	JSON string writer expecting value. (since 100.0.0)

Mapping errors

Errors related to the internal ArcGISRuntime domain and mapping APIs.

Error code	Description
7001	Spatial reference is missing. (since 100.0.0)
7002	Initial viewpoint is missing. (since 100.0.0)
7003	Invalid request response. (since 100.0.0)
7004	Bing maps key is missing. (since 100.1.0)
7005	Layer type is not supported. (since 100.0.0)
7006	Sync not enabled. (since 100.0.0)
7007	Tile export is not enabled. (since 100.0.0)
7008	Required item property is missing. (since 100.0.0)
7009	Web map version is not supported. (since 100.0.0)
7011	Spatial reference invalid or incompatible. (since 100.1.0)
7012	Package needs to be unpacked before it can be used. (since 100.2.1)
7013	Elevation source data format is not supported. (since 100.3.0)
7014	Web scene version or viewing mode is not supported. (since 100.3.0)
7015	Loadable object is not loaded when it is expected to be loaded. (since 100.6.0)
7016	Update packages for an offline map area are not supported. (since 100.6.0)
7017	Trace operation failed. (since 100.7.0)
7018	Arcade expression is invalid. (since 100.8.0)
7019	Requested extent contains too many associations. (since 100.8.0)
7020	A layer has requested more features than the service maximum feature count. (since 100.9.0)
7021	Feature service does not support branch versioning. (since 100.9.0)
7022	Packaging of data for the offline map area is not complete and it is not ready for download. (since 100.9.0)
7023	An upload sync direction is not supported. (since 100.9.0)
7024	Tile export in .tpkx format is not supported. (since 100.10.0)
7025	The specified layer does not intersect the area of interest. (since 100.12.0)
7026	Local edits must be sent to a service (using a sync direction of upload) before update packages can download a replacement geodatabase. (since 100.14.0)

Licensing errors

Errors that may occur when working with licensing.

Error code	Description
8001	Unlicensed feature. (since 100.0.0)
8002	License level fixed. (since 100.0.0)
8003	License level is already set. (since 100.0.0)
8004	Main license is not set. (since 100.0.0)
8005	Unlicensed extension. (since 100.0.0)
8006	Portal user with no license. (since 100.7.0)

Internal library errors

Internal errors related to the use of common libraries.

Error code	Description
10001	IO error. (since 100.0.0)
10002	Invalid array length. (since 100.0.0)
10003	Arithmetic underflow. (since 100.0.0)
10004	System error. (since 100.0.0)
10005	Range error. (since 100.0.0)
10006	Arithmetic overflow. (since 100.0.0)
10007	Out of range. (since 100.0.0)
10008	Length error. (since 100.0.0)
10009	Invalid argument. (since 100.0.0)
10010	Asynchronous error. (since 100.0.0)
10011	Math domain error. (since 100.0.0)
10012	Unknown error. (since 100.0.0)
10013	Logic error. (since 100.0.0)
10014	Invalid weak reference. (since 100.0.0)
10015	Invalid type Id. (since 100.0.0)
10016	Invalid function call. (since 100.0.0)
10017	Invalid error management. (since 100.0.0)
10018	Invalid cast. (since 100.0.0)
10019	Out of memory. (since 100.0.0)
10020	Unknown error. (since 100.0.0)

Hydrography and ENC errors

Errors that may occur when working with Hydrography and Electronic Navigation Charts (ENC) APIs.

Error code	Description
12001	SSE 01: Self-Signed Key is invalid. (since 100.3.0)
12002	SSE 02: Format of Self-Signed Key file is incorrect. (since 100.3.0)
12003	SSE 03: SA-Signed Data Server Certificate is invalid. (since 100.3.0)
12004	SSE 04: Format of SA Signed DS Certificate is incorrect. (since 100.3.0)
12005	SSE 05: SA Digital Certificate (X509) file is not available. A valid certificate can be obtained from the IHO website or your data supplier. (since 100.3.0)
12006	SSE 06: The SA-Signed Data Server Certificate is invalid. The SA may have issued a new public key or the ENC may originate from another service. A new SA public key can be obtained from the IHO website or from your data supplier. (since 100.3.0)
12007	SSE 07: SA-signed DS Certificate file is not available. A valid certificate can be obtained from the IHO website or your data supplier. (since 100.3.0)
12008	SSE 08: SA Digital Certificate (X509) file incorrect format. A valid certificate can be obtained from the IHO website or your data supplier. (since 100.3.0)
12009	SSE 09: ENC Signature is invalid. (since 100.3.0)
12010	SSE 10: Permits not available for this Data Server. Contact your data supplier to obtain the correct permits. (since 100.3.0)
12011	SSE 11: Cell Permit not found. Load the permit file provided by the data supplier. (since 100.3.0)
12012	SSE 12: Cell Permit format is incorrect. Contact your data supplier and obtain a new permit file. (since 100.3.0)
12013	SSE 13: Cell Permit is invalid (checksum is incorrect) or the Cell Permit is for a different system. Contact your data supplier and obtain a new or valid permit file. (since 100.3.0)
12014	SSE 14: Incorrect system date, check that the computer clock (if accessible) is set correctly or contact your system supplier. (since 100.3.0)
12015	SSE 15: Subscription service has expired. Please contact your data supplier to renew the subscription licence. (since 100.3.0)
12016	SSE 16: ENC CRC value is incorrect. Contact your data supplier as ENC(s) may be corrupted or missing data. (since 100.3.0)
12017	SSE 17: Userpermit is invalid (checksum is incorrect). Check that the correct hardware device (dongle) is connected or contact your system supplier to obtain a valid userpermit. (since 100.3.0)
12018	SSE 18: HW_ID is incorrect format. (since 100.3.0)
12019	SSE 19: Permits are not valid for this system. Contact your data supplier to obtain the correct permits. (since 100.3.0)
12020	SSE 20: Subscription service will expire in less than 30 days. Please contact your data supplier to renew the subscription licence. (since 100.3.0)
12021	SSE 21: Decryption failed no valid cell permit found. Permits may be for another system or new permits may be required, please contact your supplier to obtain a new licence. (since 100.3.0)
12022	SSE 22: SA Digital Certificate (X509) has expired. A new SA public key can be obtained from the IHO website or from your data supplier. (since 100.3.0)
12023	SSE 23: Non-sequential update, previous update(s) missing - try reloading from the base media. If the problem persists contact your data supplier. (since 100.3.0)
12024	SSE 24: ENC Signature format incorrect, contact your data supplier. (since 100.3.0)
12025	SSE 25: The permit for ENC<cell name> has expired. This cell may be out of date and MUST NOT be used for Primary NAVIGATION. (since 100.3.0)
12026	SSE 26: This ENC is not authenticated by the IHO acting as the Scheme Administrator. (since 100.3.0)
12027	SSE 27: ENC<cell name> is not up to date. A New Edition, Re-issue or Update for this cell is missing and therefore MUST NOT be used for Primary NAVIGATION. (since 100.3.0)

Navigation errors

Errors that may occur when working with Navigation APIs.

Error code	Description
13001	Service doesn't support rerouting. (since 100.6.0)

Geotrigger errors

Errors that may occur when working with Geotrigger APIs.

Error code	Description
16001	A problem was encountered with a geotrigger feed. (since 100.12.0)
16002	A problem was encountered with the fence parameters for a fence geotrigger. (since 100.12.0)
16003	A problem was encountered with the fence data for a geotrigger. (since 100.12.0)

Indoor Positioning Systems (IPS) errors

Errors that may occur when working with Indoor Positioning APIs.

Error code	Description
17000	Device doesn't support accelerometer. (since 100.12.0)
17001	Device doesn't support gyroscope. (since 100.12.0)
17002	Device doesn't support magnetometer. (since 100.12.0)

Authentication errors

Errors that may occur when working with Authentication APIs.

Error code	Description
18001	Invalid credentials. (since 200.0.0)
18002	Unable to determine generate token URL. (since 200.0.0)
18003	Token has expired. (since 200.0.0)
18004	A token or API key is required. (since 200.0.0)
18005	Invalid API key. (since 200.0.0)
18006	Invalid token. (since 200.0.0)
18007	You do not have permission to access the resource. (since 200.0.0)
18008	Secure socket layer required. (since 200.0.0)
18009	The credential cannot be shared with the request URL. (since 200.0.0)
18010	The authorization end point responded with a failure. (since 200.1.0)
18011	The authentication challenge was canceled. (since 200.2.0)

Symbol dictionary errors

Errors that may occur when working with Symbol Dictionary APIs.

Error code	Description
19000	Symbol dictionary not supported. (since 200.0.0)
19001	Missing symbol dictionary configuration. (since 200.0.0)
19002	Missing symbol dictionary script. (since 200.0.0)
19003	Missing symbol dictionary display name. (since 200.0.0)
19004	Error parsing the symbol dictionary configuration. (since 200.0.0)
19005	Error parsing the symbol dictionary script. (since 200.0.0)
19006	Error evaluating the symbol dictionary script. (since 200.0.0)
19007	Error establishing connection with the stylx file for symbol dictionary. (since 200.0.0)
19008	Error converting ordered anchor points to geometry for symbol dictionary. (since 200.0.0)
19009	Error converting geometry to ordered anchor points for symbol dictionary. (since 200.0.0)

Feature service edit errors

Edit errors are returned by the server after you call apply edits on a service feature table. The EditError (EditError) object in the API wraps these error codes and messages. Refer to feature service error codes for more information.

HTTP, network, and REST errors

Some APIs communicate with servers and services over the World Wide Web using HTTP, such as the low-level REST API. The following HTTP error codes are returned from ArcGIS services:

Error code	Description
400	The request sent to the server is not correct.
401	Authorization to the requested resource is required.
403	Authorization to the requested resource is required.
404	The requested resource was not found.
413	The request is larger than limits defined by the server. If you're trying to upload an attachment, this error might indicate that the attachment's size exceeds the maximum size allowed.
498	The access token provided is invalid or expired.
499	A token was required to access the resource.
500	The service was not able to fulfill the request, possibly due to invalid input, or the service may not be functioning properly.
501	The requested service is not implemented.

Uncategorized errors

Error

Description

ArcGIS Runtime error Invalid access range Feature service is not loaded, it needs to be loaded before passed into the sync task.

Check that the offline data you're trying to access has been created correctly and make sure you understand the offline considerations described here. A mobile geodatabase (.geodatabase file) must come either from an online feature service (from ArcGIS Online or ArcGIS Enterprise 10.x) or be side-loaded from content created by ArcGIS Desktop's Create Runtime Content tool. You cannot manually create an offline mobile geodatabase. A feature service must be sync-enabled if you want to edit it offline. Determine whether or not your service is sync-enabled by looking at the REST endpoint. A sync-enabled service has three specific REST endpoints listed at the bottom of its HTML page: 1) Create Replica 2) Synchronize Replica 3) Unregister Replica. For details on how to create a sync-enabled service on ArcGIS Online, see Managing hosted feature layers. Map services cannot be sync-enabled.