Unable to add layer to Map Viewer, but can add from REST endpoints

292
2
Jump to solution
01-21-2021 08:11 AM
Mary_GraceMcClellan2
New Contributor III

We recently deployed Portal and federated with our existing ArcGIS Server sites. Our existing services have become "Map Image Services" and "Feature Layers" within the Portal Content. When I try to open a Map Image Service or a Feature Layer in the Portal Map Viewer, I get an error that says "The layer, [layer name], cannot be added to the map." I get the same message when I open a new Map Viewer and try to add the data from my content. I checked the console output, and only saw the following warnings (no errors): 

[Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience.

DevTools failed to load SourceMap: Could not load content for https:// ... : HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

DevTools failed to load SourceMap: Could not load content for https:// ... : HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

DevTools failed to load SourceMap: Could not load content for chrome-extension: ... : HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>

I am able to select "Add Layer from Web" and paste the REST endpoint from our rest/services directory, and the data loads without issues. We are on ArcGIS Enterprise 10.7.1, and most of our services were published using ArcMap 10.6.1. All of our sites are behind a proxy server, which we rely on to handle certificates. 

If anyone has any insight, I would really appreciate it. 

 

2 Solutions

Accepted Solutions
HenryLindemann
Esri Contributor

Hi @Mary_GraceMcClellan2,  

When you open up a service in Portal do you see the Layers heading if this does not appear then it is a indication that portal can not communicate with the service.

HenryLindemann_0-1611295665396.png

If this is the case then inspect the url you do this with a tool called ago-assistant

Login navigate to the service and under "I want to" select Update the URLs of Registered Apps and Services, this will then display the URL on the right.

HenryLindemann_1-1611296096968.png

Does the displayed url match the url you are accessing in the rest? if not you can just update it with the correct url and that should fix the problem.

In ArcMap when you publish the url are you using the https://dns.com:6443/arcgis url or the Web adaptor url this should be the same url as the one with the valid certificate https://dns.com/webadaptor.

Hope it helps

Regards

Henry

 

 

View solution in original post

Mary_GraceMcClellan2
New Contributor III

Hi Henry, 

Thank you for your suggestion of looking at the service URL for the Portal items. I thought I had already done that, but when I looked again, it appears that an additional "rest" had been added in the URL somehow. I can only assume this has to do with the way that I configured Portal to communicate with Server, but I will go through and fix the URLs. Thanks again! 

View solution in original post

0 Kudos
2 Replies
HenryLindemann
Esri Contributor

Hi @Mary_GraceMcClellan2,  

When you open up a service in Portal do you see the Layers heading if this does not appear then it is a indication that portal can not communicate with the service.

HenryLindemann_0-1611295665396.png

If this is the case then inspect the url you do this with a tool called ago-assistant

Login navigate to the service and under "I want to" select Update the URLs of Registered Apps and Services, this will then display the URL on the right.

HenryLindemann_1-1611296096968.png

Does the displayed url match the url you are accessing in the rest? if not you can just update it with the correct url and that should fix the problem.

In ArcMap when you publish the url are you using the https://dns.com:6443/arcgis url or the Web adaptor url this should be the same url as the one with the valid certificate https://dns.com/webadaptor.

Hope it helps

Regards

Henry

 

 

View solution in original post

Mary_GraceMcClellan2
New Contributor III

Hi Henry, 

Thank you for your suggestion of looking at the service URL for the Portal items. I thought I had already done that, but when I looked again, it appears that an additional "rest" had been added in the URL somehow. I can only assume this has to do with the way that I configured Portal to communicate with Server, but I will go through and fix the URLs. Thanks again! 

View solution in original post

0 Kudos