nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Publish Trace as a web tool for use in WAB

ECarson

Hi,

I'm trying to publish Trace as a web tool to utilize the WAB Network Trace widget.

The Trace tool will run successfully when using the feature service, but when trying to publish the geoprocessing tool it says that the "Data source used by the Task Trace is not registered with the server and will be copied to the server: ". I don't want it copied twice as its already a feature service?

If I use the sde feature class directly the error is "ERROR 002137: This operation is not supported in client-server mode."

Can someone provide some direction on what I'm not doing correctly or another approach that they have successfully configured?

All help is appreciated.

Regards,

Elliott

Find more posts tagged with

Accepted answers

All comments

AlixVezina

@ECarson Here's an example of the steps to publish the geoprocessing service that can be used in the WAB Network Trace widget: https://solutions.arcgis.com/water/help/water-outage/get-started/generate-data-and-publish-trace.htm.

The widget cannot consume the feature service, it needs a published geoprocessing service.

ECarson

A bit more on this issue.

I have a successful published Trace Network, I can run a Trace on this network and it performs as expected.

I can Share the previously run Trace tool as a web tool. When I do share this tool whether I select the options Reference registered data or Copy all data the Analyze function produces the following warning 24032: Data source used by tool Task Trace is not registered with the server and will be copied to the server: xyz Trace Network.

After the Trace web tool has been shared, if I run it directly from the rest endpoint or from Pro as a tool I get the same error from both operations:

esriJobMessageTypeInformative: Submitted.
esriJobMessageTypeInformative: Executing...
esriJobMessageTypeError: ERROR 000840: The value is not a String.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000800: The value is not a member of No direction | Upstream path | Downstream path.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000800: The value is not a member of Both junctions and edges | Junctions only | Edges only.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000800: The value is not a member of New selection | Add to the current selection | Remove from the current selection | Select subset from the current selection | Switch the current selection.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000840: The value is not a String.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid. ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: Failed.

I've attached a few images of the inputs for the rest end point submission and tool run via pro.

If anyone could provided any helpful advice it would be most appreciated.

Regards,

Elliott

Hi Elliott,

Have you figured this out yet? We are having the same exact issue. When I tried to share the successfully run Trace as a web tool, it says source data is not registered. Blow is what we have -

We have a successfully published Trace Network.
I put the Trace tool in a model and ran it successfully. The model is located on our server.
I have the start point and barrier layers pointed to a file geodatabase on the server.

When I tried to share the model as a web tool, it gave me the warning. And it seems like it is referencing a model located in a temporary folder on my local drive. It just doesn't make sense to me. I am hoping to see if anyone has figured out a way to trace Trace Network features on a web application.

Best,

Margo

AlixVezina

@ECarson Just wanted to add that the WAB Network Trace widget only supports geoprocessing services created from a Geometric Network, the Trace Network is not supported.

MargoHuang

@AlixVezina Is there a way to trace Trace Network features in a web application? We can't seem to find any documentation about this. Thanks a lot!

AlixVezina

There currently aren't any web applications that support tracing the Trace Network. I believe your only option at this time is ArcGIS Pro or custom development against the REST endpoint Trace—ArcGIS REST APIs | ArcGIS Developers

MargoHuang

Thank you! This is good to know.

ECarson

I've had another crack at this issue through python code. Dose anyone know how to access the feature service relating to the Trace Network through AGS Server. I can access all the services through portal that make up the Trace Network with the exception of the Trace Network which is not shown in portal?

Or does anyone know how to implement the (TraceNetworkServer)?

esriJobMessageTypeError: Traceback (most recent call last): File "E:\arcgisserver\directories\arcgissystem\arcgisinput\ABU\tokenAccess.GPServer\extracted\cd\firewater\test.py", line 48, in <module> arcpy.tn.Trace(in_trace_network=trace_network,trace_type="CONNECTED",starting_points=sor,barriers=barriers,path_direction="NO_DIRECTION",shortest_path_network_attribute_name="",include_barriers="INCLUDE_BARRIERS",validate_consistency="VALIDATE_CONSISTENCY",ignore_barriers_at_starting_points="DO_NOT_IGNORE_BARRIERS_AT_STARTING_POINTS",allow_indeterminate_flow="IGNORE_INDETERMINATE_FLOW",condition_barriers=None,function_barriers=None,traversability_scope="BOTH_JUNCTIONS_AND_EDGES",functions=None,output_conditions=None,result_types="AGGREGATED_GEOMETRY",selection_type="NEW_SELECTION",clear_all_previous_trace_results="CLEAR_ALL_PREVIOUS_TRACE_RESULTS",trace_name="TEST",aggregated_points=trace_points,aggregated_lines=trace_lines,out_network_layer=None,use_trace_config="DO_NOT_USE_TRACE_CONFIGURATION",trace_config_name="",out_json_file=None) File "E:\ArcGIS\Server\framework\runtime\ArcGIS\Resources\ArcPy\arcpy\tn.py", line 671, in Trace raise e File "E:\ArcGIS\Server\framework\runtime\ArcGIS\Resources\ArcPy\arcpy\tn.py", line 668, in Trace retval = convertArcObjectToPythonObject(gp.Trace_tn(*gp_fixargs((in_trace_network, trace_type, starting_points, barriers, path_direction, shortest_path_network_attribute_name, include_barriers, validate_consistency, ignore_barriers_at_starting_points, allow_indeterminate_flow, condition_barriers, function_barriers, traversability_scope, functions, output_conditions, result_types, selection_type, clear_all_previous_trace_results, trace_name, aggregated_points, aggregated_lines, out_network_layer, use_trace_config, trace_config_name, out_json_file), True))) File "E:\ArcGIS\Server\framework\runtime\ArcGIS\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 512, in <lambda> return lambda *args: val(*gp_fixargs(args, True)) arcgisscripting.ExecuteError: ERROR 000228: Cannot open the dataset. Failed to execute (Trace).
esriJobMessageTypeInformative: Failed script tokenAccess...
esriJobMessageTypeError: Failed to execute (tokenAccess).

Any help is appreciated

JonSwoveland

Did you ever figure this out? Two years later and I'm getting exactly the same errors trying to execute a Geoprocessing Service Task published from an ArcGIS Pro Trace task against a Trace Network dataset. I'm using the barebones REST API to do this.

So frustrating.

Messages:

esriJobMessageTypeInformative: Submitted.
esriJobMessageTypeInformative: Executing...
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000800: The value is not a member of No direction | Upstream path | Downstream path.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError: ERROR 000584: Implementation of this Tool's Validate is invalid.
esriJobMessageTypeError:
esriJobMessageTypeError:
esriJobMessageTypeError: ERROR 000800: The value is not a member of Both junctions and edges | Junctions only | Edges only.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.