We're trying to take advantage of the new extract data option in the ArcGIS JavaScript API, and are testing it out using the OurServer/ArcGIS/rest/services/System/SpatialAnalysisTools/GPServer/ExtractData/submitJob REST API method.
We shared our feature class as a service (checking the Extract option for the feature service), and are trying to do a simple shapefile extract to test it out. We have started the SpatialAnalysisTools service, and are testing with the following inputLayers data:
[ { 'url' : 'OurServer/ArcGIS/rest/services/ServiceName/FeatureServer/0', 'filter': '1 = 1' } ]
Whenever we submit a job it errors out with a "Failed to execute" error. The message code is "AO_100026" and the extra log text in the system error logs is "Missing organization data store."
We have version 10.4.1 of ArcGIS server installed.
Our feature class works fine with the other REST web api methods, and the database data store has been validated. Any ideas why we are getting the missing organization data store error?
Thanks,
Steve
This is probably a bit late to help the original poster, but it might help someone else. (It certainly would have helped me!)
I was trying to export data using the Analysis Widget in Web AppBuilder. I got the same message code but our text just said "Extract data failed."
We have a federated portal and web server.
I staged the app to be ready to submit a request to extract the data and then I pressed F12 on the IE browser to get the debug helper window. (Other browsers have similar features, adjust as appropriate.)
I turned on the monitor to report on network traffic from and to the browser.
I looked for the Post command that requested the extract and saw that the extract job had been submitted successfully. I then looked for the Get command and checked its response. The response message text was equally uninformative (but in other circumstances might not be). However, it also had a JOB ID field. That info was golden, as you'll see in a bit.
I then went to our esri webserver to the gis administrator page. I picked the SITE tab and then the DIRECTORIES tab. This gave me a list of directories to look into.
In my case, the directory for JOBS turned out to be useful. It appears that all the tools that accept jobs have their own directory. In this case, it was the SYSTEM/SpatialAnalysisTools_GPServer file directory that was of interest.
I noticed a bunch of file folders inside that directory with gibberish alpha-numeric names. It turns out the file folders are named for the JOB ID!
Inside that jobs folder was a SCRATCH folder. I found a MESSAGES.XML file that turned out to be a more detailed log of the extract job. It pointed us to the python script that was failing, to the line number of the error, and gave us a more useful error message than "ExtractData Failed."
We're still tracking down what the exact problem is, but now we've got a clue. (I'll post back if/when we find the solution.)