I am rather suddenly getting this error message on a map with multiple layers and groups of layers that represent specific workflows. No idea what could have triggered it. Is there any way to recover a dead map?
Maybe try suggestions in the following post
To add to the thread, this was seen in an Esri Support case and this was their solution:ArcGIS Pro was updated to ArcGIS Pro 3.3.0 and a workaround was implemented to stop the message of "Failed to open map view."Workaround:1. Open the ArcGIS Pro project.2. Opening each map for one at a time.3. Remove the layers from that map.4. Save.5. Delete map.6. Save project.Other items that may cause this error: broken data links, an attribute table is open when saving the *.aprx (close the table and resave the *.aprx), *.aprx is on a network drive vs. C: drive, or corrupted toolbox (*.atbx) - delete and resave *.aprx.
@Robert_LeClair how does one open each map when the issue is that the map does not open?
It's a good question certainly. In the Support Case, the error message was being thrown while the map view was opening (for some reason). In this case, if one cannot open the map view, it could just be a corrupted map view and/or *.aprx. If a corrupted map view, then best to delete and rebuild it.
There is some Python scripting referenced here that the user can list out what layers are in the *.aprx and then "test" each layer in a new project to see if any of the datasources are bad.
@Robert_LeClair interesting -- I'll have to give this a try. I'm working with another user's file, and one thing I noticed when poking around in the catalog etc. was that while the map doesn't open and it doesn't have a disclosure triangle to show its layers in the catalog TOC/can't double click to see it, it does show its data sources when I use the data source manager. Is this error known to be a data source issue? Any indication of the cause within the otherwise very generic error would be potentially useful when troubleshooting.
Wow. I REALLY dropped the ball on this one. Sorry for being so unresponsive. I ended up making a new map and starting over. It was very frustrating to lose the layers I had carefully organized, but there was no other alternative and to this day, I have absolutely no idea what caused it. Thank you to all who have contributed and if anyone does know why this happens, it would be great to know.
Nothing but crickets from ESRI on this? Doesn't give me much confidence in the software if randomly your layers go away and there is no workaround.
Hi @JoeLummi - as I'm the only Esri person on this thread, it appears that the OP resolved their issue with creating a new project *.aprx - hence crickets I suppose.
Question - are you experiencing the same issue as the OP? Please advise and I'll be more than happy to do so more deep diving on the question.To add to the thread and my next question to the OP - are you using ArcGIS Pro in conjunction with cloud storage devices? If so, there's a tech support article discussing this - Problem: ArcGIS pro and Cloud Storage Services
Hi, Robert. Thanks for responding.
No, making a new copy of the APRX resulted in the same error when opening the copy. The APRX would not package throwing a heap of Layer data source is inaccessible errors.
This problem has happened to two APRX files this week. The first to fail was a base map that I do my daily work in, the second was a copied version of the first but with some data removed and renamed.
I have tried busting into the APRX with 7zip and deleting out old data from Layers folder but that had no impact.
Hi @JoeLummi - so I downloaded the *.aprx you uploaded and although I didn't have the data, I did see a "Failed to open table" warning message. I clicked OK to clear the message and then closed all of the Map and Layout Views. I then saved the *.aprx, closed ArcGIS Pro, and reopened the saved project. I did not see any messages about "Failed to open map view" as they were all closed in the saved project. I then opened each Map View individually and they all opened up albeit without any data. Are you able to replicate this workflow? If so, do you still see the warning message?
Any ideas on why this would happen?
agreed, suddenly having this issue across many pro projects company-wide. No obvious way to resolve and hundreds and hundreds of man hours to rebuild these maps, if at all possible.
@MapsInRaleigh - I would recommend that you contact Esri Support Services and open a ticket with them to work directly with an analyst.
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
