Select to view content in your preferred language

ExB unable to add from Portal

24
0
2 hours ago
Labels (1)
Bharat
by
New Contributor

Hi there community,

We are using ArcGIS Enterprise to manage a large amount of data for our department. Although we have access to AGOL, we don’t use it due to security policies. Our ArcGIS Server is hosted on s14, and the portal is on s45. When I open Experience Builder (ExB), it loads from s45.company.com/arcgis/apps/experiencebuilder/.

The issue arises when I try to add data layers; I consistently receive the error “item doesn’t exist or is inaccessible.” The browser console shows the following CORS error:

Access to fetch at 'https://s14.company.com/arcgis/rest/services/ServiceDev/...../FeatureServer?f=json' from origin 'https://s45.company.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I have RDP access to the server and found the following in the web.config file:

<customHeaders>
    <remove name="Access-Control-Allow-Origin" />
</customHeaders>

I attempted to modify the web.config to add the necessary headers, but this caused our web application running on Geocortex to stop working.

Despite adding s45 to the allowed origins on the server, and experimenting with the web.config, I am unable to resolve the CORS issue and create a functional ExB web app. We can perform these actions on AGOL, but due to security restrictions, we cannot share any data on AGOL.

Has anyone encountered a similar issue or have any suggestions on what might be missing? Any help would be greatly appreciated!

Thanks in advance!

 

Tags (1)
0 Kudos
0 Replies