nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Arcgis Pro 3.1.1 crashes trying to open .aprx

Sassafras

This is regarding Arcgis Pro (desktop) ver. 3.3.1 running on Windows 10. I am able to make .aprx files and open those that I make. I cannot open .aprx files made on another computer (from any coworker). It simply crashes. However, my coworkers are able to open .aprx files from other computers on their computers. So there doesn't seem to be anything inherently wrong with said .aprx files. In addition, I am unable to import .mxd files made from the good old Arcmap, while coworkers are able to. Any thoughts? Any software I amy be missing, like some kind of python or .net stuff?

Thank you

Find more posts tagged with

Desktop

Accepted answers

All comments

Robert_LeClair

For the coworkers *.aprx's that are crashing in your ArcGIS Pro session, do you know what release of ArcGIS Pro they are using? 3.x? 2.9?

With regards to the *.mxd import, I have not experienced this problem before. To import, you can click the Insert tab at the top, click Import Map in the Project group, navigate to where the *.mxd is located, select it and click OK. This will import the *.mxd contents into your current ArcGIS Pro project.

SeaRM

@Robert_LeClair I think the topic starter wanted to say the importing mxds also causes the ArcGIS Pro crashing. I have experienced that too. The reasons of that crashing I didn't find out, unfortunately.

Sassafras

We are all running version 3.1. They are able to import .mxd fine and open .aprx fine. My install of Arcgis Pro crashes while attempting to open .aprx file or import .mxd files.

Sassafras

That is correct, Arcgis Pro crashes while attempting to import .mxd files.

Robert_LeClair

This is not expected behavior. I would recommend that you do a clean uninstall and a clean reinstall of ArcGIS Pro. This should correct any erroneous behaviors that you're seeing in the application. I know whenever a new dot release of ArcGIS Pro is released - 3.1 or 3.2 or 3.3 - I do a clean uninstall and reinstall to avoid any issues. I know this is not ideal but in my experience does prevent a lot of errors.

BarryNorthey

This will hopefully add some perspective about the world in which I think many institutional GIS users find themselves, in particular having limited to no admin rights on their computers.

My (former) organization adopted the "managed" desktop approach to software delivery for security and IT convenience reasons, otherwise known as the "one size fits all" approach in a world where 4 GB of RAM was sufficient in their view. Software was delivered to desktops via "canned" installation packages. This worked fine for Microsoft Office and security updates but was a challenge for esri GIS software due to its size, complexity, dependencies and ongoing changes and updates.

We (I originally) had to write out detailed instructions for the "packagers" who had no knowledge of GIS and test installations on test machines and then release a preliminary package to a few "volunteers". Broader rollout was undertaken only when the kinks were ironed out. Programs and procedures were developed around a certain version of the software and changing to the latest GIS release was resisted unless deemed to be unavoidable or beneficial. We also had to be able to work with clients outside the organization. My former organization is still using ArcGIS Desktop as far as I know and one can imagine the rocky road ahead changing to Pro, which yes, should have started a while ago.

In light of this thread, a few questions come to mind. Do you have admin rights? Do you install your own software, does IT do it or does it come as a package? Does your computer meet all system requirements, how is this checked and by whom? And so on.

I realize that things work for others, but if you have ArcGIS Desktop installed, check for and repair broken links in the mxd and run the ArcGIS Document Defragmenter utility. Alternately, create a Map Package and try to import that.

Sassafras

Thank you. I just ran through the link you provided to do a clean reinstall of Arcgis pro. The errors still presist.

Sassafras

Yeah, I think you hit the nail on the head. I work for an organization that severely limits my admin rights, making fixing and installing anything a nightmare.

"In light of this thread, a few questions come to mind. Do you have admin rights? "

I do not have admin rights.

"Do you install your own software, does IT do it or does it come as a package? "

Either IT installs it or it comes in canned through a "software center" program.

"Does your computer meet allsystem requirements, how is thischeckedand by whom? And so on."

The machine meets most of the specs, lacking in the graphics card department, but its a laptop so... Nevertheless I have done alot of GIS'ing on this machine with Arcgis pro and it handles it fairly well. I think my organization tries to buy computers that mostly meet the specs at the beginning, and periodically upgrade as needed.

I will try the "ArcGIS Document Defragmenter utility". Good idea on the Map Package as a work around.

Thank you.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.