Failed to open map view

NadaKadhim · ‎09-01-2021

Hello everyone,

I have been working for 15 days on an important project. Every step/process that I was working on I saved it. When I open ArcGIS Pro (version 2.8) I found this message.

Please, could you help me in fixing this issue as soon as possible?

I'll highly appreciate your help.

Thank you.

Best regards,

SusanZwillinger2 · ‎01-23-2026

I'm running ArcGIS Pro 3.6.1 and this just happened to me. I was giving a live demo when the Map suddenly stopped displaying the layers that I was turning on via the checkbox in the Contents pane. I had Uber hexagons displaying count data with labels. Layers had displayed correctly just minutes before the meeting and then . . . nothing.

When I restarted ArcGIS Pro and loaded the aprx, I got the dreaded "Failed to open map view". I am not able to copy/paste or duplicate the offending Map, but the other 2 Maps in the project still open.

I ended up rebuilding the project on the fly to be able to do the demo, but that was far from ideal because some layers that had been based on selection logic involving multiple steps could not be done that quickly.

This software behavior is totally unacceptable and needs to be fixed ASAP. Oddly, there was also no "backup" copy of the project file. While I didn't lose any feature classes, there is a ton of work that goes into symbology, label expressions, definition queries, selection map layers, etc. To lose several hours of work is very sad.

AR_GISNinja · ‎02-03-2026

Just reiterating the problem everyone else is having... I just encountered the "Failed to open map view" error where my primary map with all crucial details no longer works, and I am having to roll all project data back to an earlier instance. All other maps and layouts work just fine, but the primary map cannot be copied, cannot be duplicated, exported, packaged or otherwise. The only option is to roll back, and thankfully that is an option for me.

I can only imagine the horror show that this would look like for a single user without a backup infrastructure who is paying big bucks for a license...

This appears to be directly tied to the new 3.6.1 update. Never encountered this prior to my recent update, the sad thing is I avoided 3.6 because I knew it would be broken- so I held out for 3.6.1 only to encounter this.