Hi all,
I'm working with two organizations who are sharing hosted feature layers via a group, I'll call them Org_A and Org_B.
Org_A has a group with a few hosted feature layers in it, some editable, some not. An Org_B user with a Pro Basic license can access these layers through Survey123 forms and the web, and can see the layers in the Catalog pane of ArcGIS Pro. However, when an Org_B user attempts to add these layers to a map in Pro they get the following message:
Failed to add data: (URL redacted)
ERROR: code 403, You do not have permissions to access this resource or perform this operation., You do not have permissions to access this resource or perform this operation., Access to this resource is forbidden, regardless of authorization.
Any ideas why would this user would not be allowed to add the data in Pro, although they can access it through the AGOL web interface, the REST Services Directory, etc.? This occurs with all of the hosted feature layers in the group, it isn't limited to one specific layer.
Thanks!
Currently experiencing this same issue-the portal data loaded into Pro without issue yesterday. Today I went to refresh the layers now I'm receiving an error. I am the owner and creator of this map so I'm not sure why I suddenly wouldn't have permission to access it. What gives?
Failed to add data: https://services8.arcgis.com/7lN2Jad9GjJFGQmU/arcgis/rest/services/(Removedforprivacy_Mapname)
Error code: 403
Description: Access to this resource is forbidden, regardless of authorization.
Message: You do not have permissions to access this resource or perform this operation.
Details: You do not have permissions to access this resource or perform this operation.
Did you ever find the cause of this issue?
I have similar problems on Enterprise 11.1 with publicly shared custom GP services... the error is the same, but the problem is intermittent. Very frustrating!
Also experiencing this issue when attempting to load hosted layers within Pro, adding either via the catalog pane or the URL pathway.
The data is shared with my organisation's AGOL via a group and a colleague with the same permissions as myself is not encountering this issue. His arcPro is 3.1 whilst mine is 3.1.4
This issue has been consistent for around 2 weeks so it not happening sporadically and is an issue with every layer.
Hi everyone,
we experienced the same thing today. OrgA has group with shared data and they add my account from OrgB to that group. But I was unable to add this data to ArcGIS Pro Map - same error as you @MobiusSnake .
Solution was simple and was caused by portal/credential mishmash. Check ArcGIS Pro --> Project --> Portals, there should be arcgis.com connection. And this connection must have login that is added to OrgA group.
It is not enough to have a connection to a specific AGOL address (e.g. xyz.maps.arcgis.com) with these credentials, but regular arcgis.com connection must also have the same credentials.
Similar Situation here. Portal-hosted Service on Federated system. ArcPro can't/won't recognize that the layer is valid, or that I am the owner of the layer. Service is still providing information to several AGOL Apps for Internal/External consumption. Enterprise 11.1, Pro 3.2.
"ERROR: code:403, You do not have permissions to access this resource or perform this operation., Access to this resource is forbidden, regardless of authorization."
It's worked for years, but this morning it refuses to act like itself.
Follow-up: Monday was horrible. For a bit over 8 hours I attempted to make any progress, without success. Wasted a bit of time reading through ESRI "documentation" not written for geospatially-minded folk... Hit an unresolvable ArcPy error in a Notebook that worked last year.
This morning, ArcPro was working as if nothing had happened yesterday. I didn't even close the project file overnight.
Was it the fault of hardware? Which hardware? Software? Which/where? Losing a day of work to a "Quirk Bug" is untenable where there are folks depending on the results of these analyses!!
...Thankfully, in my case, it was not a life-or-death situation. There are likely to be a few state legislature members who may be a bit put out. But as wide ranging and integral as ESRI has worked to make itself in every industry, you'd think a recurring bug like this one would be a high-priority for eradication.