@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?

@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?

@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: