The table below lists the extended error codes that can occur when a direct request is made to the routing service.
| Error code | Description |
|---|---|
-2147200711 | The number of input barriers exceeded the limit configured for the operation. |
-2147200712 | The number of input locations exceeded the limit configured for the operation. |
-2147200723 | The maximum number of destinations to find exceeded the limit configured for the operation. |
-2147200725 | The extent of the input locations exceeded the maximum geodesic distance configured for the operation. |
-2147200727 | The solve operation timed out prior to completion. |
-2147200737 | An error was encountered during initialization of dynamic traffic data. |
-2147200747 | The Travel cost matrix operation does not support origins in different time zones when the TimeOfDay value is specified and timeOfDayIsUTC is set to false. Set timeOfDayIsUTC=true. |
-2147200752 | The TimeOfDay value is after Dec. 31, 9999. |
-2147200753 | The TimeOfDay value is before Jan. 1, 1900. |
-2147200758 | Unable to perform conversion between time zones. |
-2147200910 | The attribute parameter value is invalid. |
-2147200939 | Invalid input to routing service direct request. |
-2147200971 | No solution found. This occurs when the operation couldn’t find any valid routes from any of the input locations. This includes the routes between input locations greater than the cutoff value. |
-2147200989 | Invalid network analysis context. |
-2147200991 | Cannot bind to the network dataset. |
-2147200995 | Insufficient number of valid input locations. In this case, the operation cannot solve or run the analysis. |
-2147201004 | The solver ran out of memory. |
-2147201019 | No result was found. |
-2147201021 | The cost attribute does not exist in the network. |
-2147418113 | This is a generic error code for when an error occurred. |
-2147467259 | This is a generic error code for when an error occurred. |