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; } } }

Failed to Import mxd to ArcGIS Pro

LesiMai3

Hi,

I was trying to import .mxd created using ArcMap 10.4.1 to Pro 1.3. After selecting the map document, Pro just shuts down automatically. I tried importing .mxd created in ArcMap 10.2, and the same thing happened.

Did I miss something here? Any help will be appreciated!

Thank you!

Find more posts tagged with

Accepted answers

All comments

Arne_Gelfert

Did you ever try and look at the ImportLog that gets created in your "ImportLog" folder inside your project folder? It might reveal some error message (or then it might not...).

KoryKramer

Michael, sorry you're having problems importing mxds into Pro. At this point, it might be more productive to get in touch with Technical Support so they can help troubleshoot. Esri Support Contact Support

MichaelHuber

Thanks for your suggestion! I wouldn't say my mxds are very complex.. one of my maps I am trying only has 8 features in it so I'm pretty baffled as to what is causing it to fail.

I'll keep trying different mxds to try and figure out what is causing it. If anyone has any other suggestions please let me know!

Table of Contents for MXD .

mvolz47

Is this a complex mxd? Maybe try importing a simpler mxd. Some items that might cause problems would be annotation layers or more complex symbology.

MichaelHuber

I just upgraded to 2.4.2 and I am unable to import a huge selection of my mxd's in ArcPro. I've tried mxd doctor with no luck. Is there anything specifically that may be restricting me opening my mxd in Pro? I was hoping to avoid rebuilding my maps from scratch. Not to mention I have completely had it with ArcMap Legend exporting issues. pro 2.4.2 import_error import mxd

LiviaBetancourtMazur

I also had this problem. Was running Pro 2.1. Upgraded to 2.2 and it worked. Not sure if that well help anyone else having this issue.

mvolz47

If the import failed message provided some feedback that would be at least a starting point, however I can not see any information as to specifically why it is failing.

That sounds like a new Idea for GeoNet to have in trouble-shooting this issue.

Anonymous User

I have not run the MXD Doctor as the mxd's open and function completely fine within ArcMap. As I test I suppose I could, however seems unnecessary given the mxd's don't appear to have issues other than the Pro import. I would not consider them to be complex mxd's, more or less just standard stuff.

If the import failed message provided some feedback that would be at least a starting point, however I can not see any information as to specifically why it is failing.

mvolz47

Did you run MXD Doctor on the problematic mxds?

Also, are you trying to import complex mxds? If so, maybe try a simpler mxd or create a simple mxd and see if the import works on that.

Anonymous User

I am also having this same issue with several mxd's at 10.3 failing to import into Pro.

I have tried everything short of completely rebuilding them from scratch in Pro which I am avoiding doing if possible, however nothing has worked. I also tried saving the mxd up to 10.5 and that failed as well. I am finding very little information online and nothing within the application as to the reasoning why it is failing. Additionally, I have tried importing the same mxd's from more than machine (different Pro installs) still no luck.

This morning I upgraded to Pro 2.1, although that still failed to import.

LesiMai3

Hi Robert,

I tried both approaches and it still doesn't work. To double check, I switched to another machine and imported the same .mxd. And this time, it works! So it's something on my end.

Thank you for all your help!

Lesi

Robert_LeClair

Hi Lesi -

Okay - save your *.mxd out to a new *.mxd document file. Import the new one into Pro. Another option is to use the MXD Doctor located in the Start>All Programs>ArcGIS>Desktop Tools and see if there's an issue with the *.mxd itself.

LesiMai3

Hi Robert,

I originally did try to import .mxd saved with the layout view open. So I followed your suggestion and tried multiple .mxds saved with the data view open. But Pro still doesn't seem to be cooperating.

Thank you!

Robert_LeClair

Question for you: Is the *.mxd saved with the layout view open/primary window? If so, switch to Data View, save the *.mxd, and attempt to import the *.mxd into Pro again. What is the result?

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.