Skip to main content
Question

Read Feature service ArcGIS Portal

  • September 17, 2020
  • 4 replies
  • 120 views
annekathrine

Hi,

I have some troubles reading a Feature service within ArcGIS Enterprise Portal, and I get the message: ArcGIS Portal Feature Service Reader: Encountered an unexpected error. The error code from the server was '500'.

If the screenshot here is to small I have also attached it.

esri

I believe the error happens when requesting metadata from the service as it calls att http instead of https (https is correct for the feature service URL). However, I don't know how to control this, as the connection to the Portal seems fine inside the Reader. I am also able to publish at new feature service to the Portal (which makes me eliminate connections problems).

 

Has anyone experienced the same thing?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

M
Forum|alt.badge.img+2
  • markatsafe
  • September 18, 2020

@Anne Kathrine Wenaas Ribe​ FME makes a request for the metadata and it is the portal that returns the metadata URL which could be either HTTP or HTTPS. I don't think this is the cause of the error. In most cases we would get a clear error that HTTPS was needed.

It looks like the error is caused by a call FME request to get the list of feature ID's :

INFORM|ArcGIS Portal Feature Service Reader: Querying layer/table 0 for object IDs, where '1=1'

and you'd expect to see something like:

INFORM|ArcGIS Portal Feature Service Reader: Got 25 results for layer/table ID 0

 

You could test this using the Portal REST API and query layer 0 for object IDs only, where 1=1 and check the json response. Something along the lines of:

https://<host>/server/rest/services/Hosted/Canada/FeatureServer/query?layerDefs={"0":"=1"}

annekathrine
  • annekathrine
  • Author
  • September 21, 2020

@Anne Kathrine Wenaas Ribe​ FME makes a request for the metadata and it is the portal that returns the metadata URL which could be either HTTP or HTTPS. I don't think this is the cause of the error. In most cases we would get a clear error that HTTPS was needed.

It looks like the error is caused by a call FME request to get the list of feature ID's :

INFORM|ArcGIS Portal Feature Service Reader: Querying layer/table 0 for object IDs, where '1=1'

and you'd expect to see something like:

INFORM|ArcGIS Portal Feature Service Reader: Got 25 results for layer/table ID 0

 

You could test this using the Portal REST API and query layer 0 for object IDs only, where 1=1 and check the json response. Something along the lines of:

https://<host>/server/rest/services/Hosted/Canada/FeatureServer/query?layerDefs={"0":"=1"}

Hi @Mark Stoakes​ ,

 

Thanks for your reply! I got a resonse from the rest api - it does not look like there is anything wrong with the sercive at least. Query should be 1=1 I think?

 

I tested reaching the service via Esri arcgis server feature server reader instead of Esri arcgis portal feature server reader, then I could read it. Then the limitations might be inside the portal?

M
Forum|alt.badge.img+2
  • markatsafe
  • September 21, 2020

@Anne Kathrine Wenaas Ribe​ All I can think off is that your portal is returning http and it should be returning https when the url is return. In your test with the rest api, did you use http or https?

 

M
Forum|alt.badge.img+2
  • markatsafe
  • September 21, 2020

@Anne Kathrine Wenaas Ribe​  Just to clarify that a little further:

Your REST API call would look something like:

https:<host>/server/rest/services/Hosted/Canada/FeatureServer/0/query

and then in the form you could enter:

2020-09-21_16-04-42

Community Stats

32,154
Posts
122,043
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.