Map Image Layers and Feature layers fails to open in Map Viewer?

Question

We have ArcGIS Enterprise 11.3.

The users in Portal are not able to view Map Image Layers, and Feature Services in Portal Map Viewer. But, the same layers can be opened and viewed in Map Viewer Classic.

With Map viewer, when a user selects an option to open in Map Viewer, a blank page opens, without displaying anything except the untitled map header.

Opening Map Image Layer in Map Viewer:

Opening same Map Image Layer in Map Viewer Classic works:

Note: This issue does not happen if we use the creator user type and admin role, and also if an admin saves the above layer as a web map, the web map opens up without any issue for viewers.

Issue observations:

User TypeRoleIssue Reproduces (Yes/No)CreatorPublisher, Editor, ViewerYESViewerViewerYESCreatorAdministratorNoCreatorCustom role (Viewer + One of the Admin Privileges( Content: View All Content))No

If I have the custom role created importing privilege's from the default viewer, Enabling only this one admin privilege's lets a user open these services without any issues in new Map Viewer, BUT, if I enable this admin privilege, it is non-compatible with Viewer User Type(which is by design), so we are stuck on this.

It would be great if someone can help us with this issue!!

Thanks you.

Yogesh_Chavan · Answer

Thank you @TimoT for looking.

To answer your queries:

Any errors in server logs or browser dev tool logs?

No

Are the affected services hosted / stored in your servers, or referenced from elsewhere?

They are from our server, and its happening with all the map image layers and feature services, it is not specific to any service!

Check and compare the header request in browser dev tools between map viewer and classic. Does the request to service look any different?

Same response on dev logs for both

Something you can check - Go to the server admin endpoint, navigate to an affected service, edit its JSON config, and find the item ID in JSON. If the ID doesn't match the one in your portal as expected, then the service is checking permissions against the wrong item.

It is matching on admin and portal

TimoT · Answer

Any errors in server logs or browser dev tool logs?

Are the affected services hosted / stored in your servers, or referenced from elsewhere?

Check and compare the header request in browser dev tools between map viewer and classic. Does the request to service look any different?

Something you can check - Go to the server admin endpoint, navigate to an affected service, edit its JSON config, and find the item ID in JSON. If the ID doesn't match the one in your portal as expected, then the service is checking permissions against the wrong item.