Data Extract Widget Error (esriJobFailed)

[JonFisher]

Hi,

I've found an interesting error with the Data Extract Tool. If the area you select to download is at all off of the edge of the map, you get an "esriJobFailed" error. The attached picture showing the error and an example selection box (below the error message, note that in an attempt to select a feature right on the edge I went slightly out of the map boundary).

My concerns are twofold: 1. The error doesn't let the user know why the request failed. 2. It is difficult to select all features right up to the edge of the map without going a bit over to be safe, even if you know about the limitation.

Any chance this could get fixed for the next FlexViewer update? Or can anyone else suggest code to fix it? Perhaps at least for the rectangle selection tool a rule could be added saying that if one of the bounding coordinates of the selection box is off the edge of the map, reset that coordinate to the edge? For non-rectangles it would be less simple but should still be achievable.

[LisaArnold]

Did you ever find a fix to this? I am receiving the same error message, although not just when the selected area is off the edge of the map. I am receiving this error when I try to extract my entire data set. The entire data set includes 3 layers, 1 of which has ~12,000 features, another has ~1,200 records. I have increased the server return limit on the map service and the geoprocessing service to 15,000 to accommodate for all the features in the entire data set, but am still receiving the job failed error.

Any ideas on why this error is coming up? I am able to extract smaller areas of the data.

[JonFisher]

I never figured out why drawing an extent off the map causes issues, so for now I just modified the code to put in a disclaimer label that the area drawn must be within the edges of the map.

I've also had trouble sometimes with downloading entire datasets. One thing to check is the timeout setting for the map service. If the extract takes longer than that it will fail.

[JonFisher]

I can confirm that in my case, I had to increase "The maximum time a client can use a service:" to 30 minutes (1800 seconds), as the default of 10 minutes (600 seconds) was not long enough to complete the task. Once I bumped that up (edit the service, go to Pooling) I've had no trouble with it crashing.