Specific Machine Cannot Open Map Service Attribute Table in ArcGIS Pro

[CalvinHarmin]

I have an individual user/machine using ArcGIS Pro 3.1.x that has an isolated issue:

When a public map service is added to a map in ArcGIS Pro on this machine, whether via Portal content menu or via adding REST URL directly, the layer(s) display correctly, but when you right-click a layer, there is no 'context menu' option for opening the Attribute Table. When right-clicked, there is literally nothing that happens or displays. 

All other machines I've tested show normal behavior of right-clicking and having the attribute table option. 

User has restarted Pro, tried whether logged in to our Portal or not (the map service(s) are public anyway), restarted computer, now we are at the step of finding some other troubleshooting step or potentially re-installing Pro if we can't figure it out.

Any ideas?

[CodyPatterson]

Hey @CalvinHarmin 

If it's a consistent version with the others and has worked on other machines, you may need to reinstall Pro as a setting change or user setting could be causing the added content to act like that. You may also consider a soft reset like this here: https://support.esri.com/en-us/knowledge-base/how-to-perform-an-arcgis-pro-soft-reset-000027631

Cody

[CalvinHarmin]

Thank you we will try soft reset steps and report back if that solves the issue.

[Robert_LeClair · Accepted solution]

If all other user/machines are not at ArcGIS Pro 3.1.x and are at a higher release, then I believe it's this item from Esri Support Services cases:  In ArcGIS Pro 3.1, one cannot access the attribute table of the sub-layers within a map service.  This functionality was introduced at ArcGIS Pro 3.2.  If possible, upgrade the user/machine from 3.1 to 3.2 or higher to have this functionality.

[CalvinHarmin]

Ah! That could be it; newer installs in our org are 3.2x in our currently. This user may have an older machine/deployment and just need the upgrade then, I will double check the other machines I tested are in fact 3.2x.

[CalvinHarmin]

Upgrading from 3.1x to 3.2.5 has solved the issue. I did not attempt the soft reset and instead jumped right to trying the 3.2x update. Thanks for the pointers!