Latest Contributions by RussCoffey

Our ArcGIS 11.3 Server regularly throws many of the following SEVERE errors (versions 11.2 and 10.9.1 did this as well): "Instance of service '....' failed to process a request."  This specific error is generate by an APRX which references 7 map services and is used by about a dozen editors to edit the Utility Network through one of the 7 services (the other map services are not editable and do not have a Feature Service enabled). The errors are thrown from layers in the Table of Contents which have a Data Source Type of "Feature Service Feature Class" which are layers referenced individually (their Layer IDs are in the URL). Data that is drawn by referencing a full Map Service does not throw this error. The errors appear to only be thrown on the initial load of the APRX into ArcGIS Pro. Other actions (pan, zoom, change version, start editing, save edits, etc.) have not been found to throw the error..... With a dozen editors opening the APRX multiple times throughout a work day, and each time throwing 5 SEVERE errors, this amounts to hundreds of SEVERE errors in the logs each day. We have noticed that each occurrence of this SEVERE error is also accompanied by a WARNING error: "Unable to process request. Error handling schema request: java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.esri.arcgis.discovery.servicelib.AGSException: java.io.IOException: Server object extension 'validationserver' not found." And fewer times, this WARNING:   "Unable to process request. Extension not found." For reference, here is a screen shot of the errors from ArcGIS Server:          The errors do not appear to have any user impact, and they do not prevent editors from doing their work.  At this point, we believe the SEVERE and WARNING errors in the logs are not something we need to be too concerned about, but the issue remains that since there are so many of them, they tend to crowd out what may be other "real" SEVERE errors that need to be handled. So the question is how do we eliminate these SEVERE errors from the logs?  It seems like two solutions may be needed here.  One for the map services which are just simple Map Services, and one for the editing service. Most of the services throwing this error are basic map services.  Why would ArcGIS Pro or ArcGIS Server be looking for a Validation Service on a map service that has no editable layers, is not versioned, has no topology or anything else that I am familiar with in relation to the purpose of a Validation Service? The Utility Network map service is, of course, running over a branch versioned dataset, so do we just turn on a Validation Service?  But we can't do that in ArcGIS Server Manager - the checkbox is always greyed out.  It appears a Validation Service is applied when the software feels that it is warranted.  For example, when we publish a Feature Class with Topology as a Map/Feature Service, it automatically gets a Validation Service applied. Thanks for any help or ideas, or even questions to help clarify this long and rambling problem description.     ... View more

Scenario: a user is capturing a line feature in the field in Field Maps.  The line needs to be a specific length because the user has measured it in the field.  (Note that high-accuracy GPS-collection does not work here due to obstructions.)  The user clicks a starting point.  Field Maps starts drawing a dashed line between that starting point and the map cursor as the user moves it around.  The user needs to place the next vertex so that the line is a specific length (say 10.5 feet). We envision two possible solutions within the Field Maps app. 1 - the cursor displays the length that the line would be if the user clicked "Add Point" at that location.  So, as the user moves the map around and the line gets shorter/longer, the length displayed would change and once it showed 10.5, the user would happily place the vertex.  (Sample screen shot of this solution is attached.) 2 - After clicking the starting point, allow the user to enter a length (in map units) for the line, and Field Maps locks the line length to that distance (acting like a radius around the starting point), until the user clicks for the second vertex.   ... View more

The short version:  Excel (using Maps for Office) can see our internal geocoding services, which are exposed as Geocoding Utility Services through ArcGIS Online, but it never actually calls them with the data to be geocoded. Now more detail: We have a few geocoding services running on our internal ArcGIS for Server servers (behind our firewall).  These services are exposed to ArcGIS Online and shared with all members of our organization.  These locators work fine in our ArcGIS Online maps and apps.  However, the locators are not called in Excel with the "Add Excel Data" tool.  The locators are visible and can be selected and the user can even specify which columns belong to which parameters for the service and the service acts like it is running, but it always returns 0 results. Watching the calls in Fiddler shows that Excel interrogates the correct internal REST endpoint to get the parameters of the selected locator, but no call is ever made to the internal geocoding service with the actual data to be geocoded. I have seen a number of somewhat related posts but no resolutions.  Anyone have a similar experience, or is anyone successfully utilizing local geocoding services from within Maps for Office? Possible issue/resolution: The option "Allow Batch Geocoding" for our services is grayed out in the ArcGIS Online "Utility Services" configuration area.  This is the path I am pursuing at the moment. ... View more