Skip to main content
Solved

ArcGIS Online Feature Service Reader Error, how to get more information?

klaasfme
Contributor
Forum|alt.badge.img+1

Hi, I have a bunch of workbenches which routinely read layers from our AGOL environment. 

There are multiple readers in the same workbench, all reading different layers. Until recently everything was doing fine, but now one reader is throwing an error. See part of the log here:

ArcGIS Online Feature Service Reader: Querying layer/table 8 for object IDs, where '1=1'
ArcGIS Online Feature Service Reader: Got 731 results for layer/table ID 8
ArcGIS Online Feature Service Reader: Splitting reading of 731 features into 1 batches of up to 1000 features
ArcGIS Online Feature Service Reader: Getting feature results 0 up to 1000 of layer/table 'tekentools polygon lopend'
ArcGIS Online Feature Service Reader: Encountered an unexpected error. The error code from the server was '400' and the message was: 'Cannot perform query. Invalid query parameters.'. Details: 'Unable to perform query. Please check your parameters.'
 

I checked the source layer in AGOL and nothing has changed for the last 5 years, so that can't be the problem. As far as i know nobody changed anything in the query or workbench. I tried messing with the query parameters with no success. I'm at a loss here.

Does anybody has an idea how to proceed debugging this? Or how to get more information other than the error message i'm getting right now? Such as the specific parameters causing trouble?

Best answer by j.botterill

400 is suggesting bad syntax, so to me it is likely the DATA having an issue being parsed in HTML to the. arcgis REST api.

So you can feature cache a partial run up to the Feature Reader where the problem is. Inspect all the attributes going into initiate the reader. If an attribute is used in the where clause, inspect the attribute column in question and INSPECT the values. Perhaps there’s a special character in the text. If you find some, paste screen shots here and include the parameters of the problem FeatureReader

View original
danilo_fme
1 person upvoted this
  • danilo_fme
    danilo_fme
Did this help you find an answer to your question?
<strong>This post is closed to further activity.</strong><br /> It may be a question with a best answer, an implemented idea, or just a post needing no comment.<br /> If you have a follow-up or related question, please <a href="https://community.safe.com/topic/new">post a new question or idea</a>.<br /> If there is a genuine update to be made, please contact us and request that the post is reopened.

5 replies

panda
Enthusiast
Forum|alt.badge.img+18
  • pandaEnthusiast
  • Enthusiast
  • May 24, 2025

Can you provide the feature service link that giving you issue, so I can take a look on my end? and you have have Where clause or anything filtering when running the feature service?

j.botterill
Influencer
Forum|alt.badge.img+40
  • j.botterillInfluencer
  • Influencer
  • Best Answer
  • May 26, 2025

400 is suggesting bad syntax, so to me it is likely the DATA having an issue being parsed in HTML to the. arcgis REST api.

So you can feature cache a partial run up to the Feature Reader where the problem is. Inspect all the attributes going into initiate the reader. If an attribute is used in the where clause, inspect the attribute column in question and INSPECT the values. Perhaps there’s a special character in the text. If you find some, paste screen shots here and include the parameters of the problem FeatureReader

klaasfme
Contributor
Forum|alt.badge.img+1
  • klaasfmeContributor
  • Author
  • Contributor
  • May 26, 2025

Thanks for the replies guys.

 

​@panda there is no where clause, everything is set to default. I cannot provide a link right now, you need a token for access and I will have to ask higher up to provide it. Thanks for the offer though! 

​@j.botterill the reader is at at the start, there is no attribute going in. I even tried adding another instance of the reader in a empty workbench. All parameters were set to default and still no luck. I think you are right here with it being a DATA issue, not an FME issue. I'm going to run some tests on the data first. Will let you know if I figured it out.

UPDATE:

So I added a WHERE clause and due to excluding data I didn't get an error. After that I filtered on objectID till I found the features that were causing the error. I found 2 features that caused the error. However I could find nothing out of the ordinary about these features. I ran some tests on them checking if the geometries (polygons) were valid and if any special characters were to be found, but I could find nothing special. So it is still a mystery to me. For now I just exclude them as a workaround, but if anyone has more diagnostic ideas it is always welcome!

panda
1 person upvoted this
  • panda
    panda
panda
Enthusiast
Forum|alt.badge.img+18
  • pandaEnthusiast
  • Enthusiast
  • June 2, 2025

​@klaasfme I think I had something similar. For me, it was that even though, it showed valid geometry in geometry validator. Sometimes the shape of that features it self are a polyline and not polygon or it was so small that it causing an error. Another one is, when someone accidentally create extra record when open it in ArcPro attribute table. (this should show up everything as null thou. but might worth a check). But if you could export those 2 out and remove any important data out of it, maybe we can help troubleshoot.

klaasgrover
Participant
Forum|alt.badge.img
panda wrote:

​@klaasfme I think I had something similar. For me, it was that even though, it showed valid geometry in geometry validator. Sometimes the shape of that features it self are a polyline and not polygon or it was so small that it causing an error. Another one is, when someone accidentally create extra record when open it in ArcPro attribute table. (this should show up everything as null thou. but might worth a check). But if you could export those 2 out and remove any important data out of it, maybe we can help troubleshoot.

I exported the two features as a geopackage and added them. Thanks for willing to put in the effort to help me troubleshoot!

This is the collection of features, 3 of them work fine and two are giving trouble. The troublemakers are the ones with global id: {C73531E8-91B3-4B15-879D-EAD386974096} AND {8581C954-6FB6-4ACA-A1F8-BF409F54EDE2}

1 Attachments

Helpful Members This Week

Community Stats

31,439
Posts
119,170
Replies
39,053
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.