Data Extract Issues
Once we upgraded to Silverlight 1.5 the Data Extract workflow stopped working. It was a pretty simple workflow to set up the first time so I just rebuilt it but of course now it doesn't work. I don't know where I went wrong. Right now the workflow brings back an empty box for the list of layers that can be extracted. Any help is appreciated.
-
Hi Zarani,
I tested the Extract Workflow with Silverlight Viewer 1.5 and it works fine. There is probably something unusual happening in your site configuration.
One thing I recommend is to grab a couple of Log Activities from Debug section in Workflow Designer and insert them before and after DynamicExternal Activity inside "Select Extract Layers" sequence.
In first one log the value of gpInfo and in the one after DynamicExteral, log the value of allLayers variable.
Then run the workflow again and check your server logs. If there were any errors in the logs that didn't make sense or didn't help you enough to troubleshoot the issue yourself, send the logs to our support center and we will investigate the issue.
Cheers
Dan
0 -
hello, i would like to implement the extract data workflow, but i am having trouble finding instructions either in overview or detail describing how to do this. It sounds like its a core feature?
i found some workflows, REST Elements\Sample Sites\Resources\Workflows\CharlotteOperational
they look like they are using a GP service instead of Essentials API or Workflow to extract.
Can anyone please at least provide a short overview, few short steps of the process of setting this up?
thanks,
--Bryan
0 -
Bryan,
It's not a actual activity built in to Essentials Workflow; however, it does use the native ESRI geoprocessing routine. Here are some rough steps to follow:
1.) Open your ArcMap document and expand ArcTollbox panel.
2.) Under "Server Tools" toolbox expand "Data Extraction" and dag and drop either "ExtractDataAndEmailTask" or "ExtractDataTask" geoprocessing routines to your table of contents. This will add the geoprocessing routine as a tool layer to the document. I typical place this at the end of the document.
3.) Not sure if this can be published as a MSD or needs to remain a MXD, but when you publish the document it will create two services, one for the map service and one for the geoprocessing service.
4.) Locate the two Extract workflows located in the default Essentials install path:
C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sample Sites\Resources\Workflows\CharlotteComplete
5.) Open the workflow and modify to use the services you just published.
6.) Add the workflow to you site and then add a button to the toolbar that calls the workflow by the ID.
That should be a good starting point to get you going.
Aaron
0 -
Bryan,
ESRI has an example in their help system that steps through the set up of a data extract geoprocessing task. Check out the "(http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/index.html#//00930000003t000000) GP Service Example: Clip and Ship " for detailed instructions.
Steve
0 -
wow, very much appreciated, thanks Aaron and Steve!!!
0 -
Hi
With regard to the Data Extract Tool I am having problems. I have followed all the instructions correctly.
Essentials 3.7 Silverlight Viewer 1.4
The tool works in Essentials up to step 2 then starts processing but returns an error.
Workflow Error
[HttpWebRequest_WebException_RemoteServer] Arguments: NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&version=4.0.50917&File=System.Windows.dll&key=httpWebRequest_WebException_RemoteServer
Windows Application Logs
An unhandled exception occurred and the process was terminated. Application ID: /LM/W3SVC/1/ROOT/Geocortex/Essentials/DevelopmentInternal/REST Process ID: 4800 Exception: System.ArgumentException Message: Value does not fall within the expected range. StackTrace: at ESRI.ArcGIS.Client.Utils.JavaScriptObjectDeserializer.DeserializePrimitiveObject() at ESRI.ArcGIS.Client.Utils.JavaScriptObjectDeserializer.DeserializeInternal(Int32 depth) at ESRI.ArcGIS.Client.Utils.JavaScriptSerializer.Deserialize(JavaScriptSerializer serializer, String input, Type type, Int32 depthLimit) at ESRI.ArcGIS.Client.Tasks.Utils.JSON.ArcGISJsonReader.GeometryServiceJsonToGraphics(String json, Nullable`1 geomType, SpatialReference sr, Int32[]& CutIndexes) at ESRI.ArcGIS.Client.Tasks.GeometryService.simplify_Completed(Object sender, RequestEventArgs e) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Application.RunInternal(Window window) at Geocortex.Workflow.Runtime.WorkflowController.b() at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
Any assistance in resolving this problem would be appreciated.
I have created a new Essentials Site just to run this workflow but same problem.
Thanks John
0 -
Coming in late on this one - but has anyone got raster layers to extract? I currently have a Raster Catalog set up in my data extract / GP mxd, and the workflow does not want to recognise this layer for export. ie. it does not present the raster output formats as options in the list so I can only assume it is not recognising it as a 'raster' layer.
any thoughts appreciated.
PS. the vector based layers are working fine!
regards
Gareth
0 -
Hi Gareth,
I have not been able to get raster layers to extract. Raster extract hasn't been a requirement of our projects so far, so I forgot about it until I saw your message. My experience mirrors yours in that the raster layer wasn't recognized as a raster layer.
At the moment I'm working on our AGS 10.1 upgrade, I might revisit the raster issue when that is finished.
Steve
0 -
Cheers Steve, thanks for the feedback.
I've let our local distributor know about the issue so we'll see what they come up with?
GF
0 -
Hi Everyone!
Recently we upgraded by getting a brand new server, with ArcServer 10.1, Essentials 3.15.1 & Silverlight 1.10 installed, and a s a result the ExtractData Geoprocessing Service can no longer be published inside an MXD.
So instead I published the Geoprocessing Service seperately and got everything working, however I noticed something that was cause for concern.
When it gets to the very end & you press "Download", our server's private URL [http://server:6080/arcgis/rest/services] flashes when its consuming the Geoprocessing Service.
This is because I can't get the Workflow to recognize the public facing URL for the Geoprocessing Service.
ALso, inside the Essentials Manager I can't get it to recognize my public facing URL for the Map Services either.
Is this an issue with the new ArcServer 10.1 Web Adapter, or is this an issue with Essentials/Proxy settings? Or maybe something else i'm missing?
Any insight on this would be extremely helpful, thank you!
-Laura-
0 -
Are you sure that your firewall isn't blocking port 6080 to your new server? That would probably be the first place I look.
Did you install the Web Adaptor? If you didn't, then you will need server:6080, but if you DID, you won't need to specify the port number. ie, like you had with Arcserver <10.0
Perhaps telnet to port 6080 on the ArcServer to see if you can connect... Or try and access your rest services from that machine. If you can't access from your Essentials server, but can from other public sources, I would be inclined to say that it is indeed a firewall issue.
0 -
It turns out we needed to update our Hosts file on the server so it recognized that the public & private URL's were the same server. Joy! Thank You -Laura-
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
12 kommentarer