Select to view content in your preferred language

ArcGIS Server SEVERE error "Instance of service '....' failed to process a request."

649
5
09-24-2024 04:17 PM
RussCoffey
Occasional Contributor

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:

        RussCoffey_0-1727219139163.png

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.

 

 

5 Replies
JasminePrater
Frequent Contributor

 We are having the same problem with our new Enterprise setup and have not been able to find a resolution.  Hopefully, someone here can help us find some answers.

miyukioki
New Contributor

We are having similar problem in Enterprise 11.3.

In our case , error occurs in Branch versioned StandalneTable type to Published as FeatureService .

SERVER ERROR: service foo.bar.MapServer instance crashed.

MasaoMatsuoka
Regular Contributor

I found out there is an enhancement request ENH-000137900: Improve the ServerValidation capability to no longer display errors in the ArcGIS Server logs nor have ArcGIS Pro call the ServerValidation endpoint if the capability is not enabled during publishing.

It says it is implemented in 3.4. Hopefully that is true.

Masao Matsuoka
RussCoffey
Occasional Contributor

That sounds promising, Masao, thank you for the information!

0 Kudos
JasminePrater
Frequent Contributor

Not particularly helpful, but I did find a bug report for the second error that seems to go in tandem with the error you are referring to.  It is "In Review", but does not seem to have any further guidance.

https://support.esri.com/en-us/bug/arcgis-server-returns-the-following-error-message-in-th-bug-00013...

0 Kudos