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

Unable to Import MXD into Arcgis Pro

UserJJC19

Trying to Import a .mxd into Arc pro, keep getting unable to import with no explanation. I have ran through MXDDoctor, with no faults found. have tried it save in data view and layout view. Everything is save in-between two geodatabases and source to local Drive. have to have 2 databases for project. all images in layout are also save to local drive as well. Using 10.7 ArcMap and 2.9.2 arcpro.

Error.jpg

wayfaringrob_0-1720731780842.png

タグ付きの投稿をもっと見る

Accepted answers

All comments

Robert_LeClair

One thing to try is in ArcMap, create a Map Package (*.mpk) and import that into a new ArcGIS Pro project. Does that workflow work?

OR -just learned this trick - in ArcMap, in the Catalog window, find the *.mxd in question and drag the from the ArcMap Catalog window and drop it in the Catalog Pane in ArcGIS Pro. That will import the *.mxd file too!

UserJJC19

Either one of those ways worked, same result unable to import

IlkaIllers1

Hi, I am experiencing the same problem:

Neither "Import Map" nor the drag&drop of the mxd into the Catalog Pane works. Both result in the same error message without error code. Additionally, after trying to import the mxd, the aprx is frozen and needs to be shut down via the task manager.

We tried the mxd Doctor, the Document Defragmenter, removing all sorts of links and packaging as a map package (both with and without the data). Nothing worked.

Other mxds work fine. It is just a collection of mxds in one folder. The special thing about these mxds is that a couple of weeks ago, there was a versioning conflict between different versions of ArcMap: on our local machines, we had a new version of ArcMap while on the cloud virtual desktop, there was still the old one. One mxd that was opened on a local machine with the new version was saved. Switching back to the old version on the cloud virtual desktop, all mxds in the folder could not be opened anymore - even though just one of them had been saved with the new version. After about a week, the new version was installed on the cloud virtual desktop, and the problem seemed to have been resolved - until now, where we are unable to import the exact same mxds into an aprx.

@Robert_LeClair , have there been more reports on this? Any ideas on how to fix this? Thanks!

Robert_LeClair

llkaillers1 - I scanned the internals trying to find any similarities of your described workflow to cases and did not see one. One thing that helped other customers when experiencing import map issues was to do a complete uninstall and reinstall of ArcGIS Pro. This resolved several cases of import map issues. Might be worth a try. If the uninstall/reinstall does not work, then it may be worth a Support Services call.

FredericPoliart_EsriAU

This issue is still happening in ArcGISPro (arcPy) :

aprx = arcpy.mp.ArcGISProject(template_aprx_path)

new_map = aprx.importDocument(mxd_path) ## << blocks in here and never returns nor times out.

bizarrely , if I import those .mxd in ArcGIS Pro (manually), it sometimes works and sometimes also times out and freezes ArcGIS Pro altogether.

I have thousands of MXD to import & scan, so I cannot do this manually.

Example APRX-Tree-Viewer:

FredericPoliart_EsriAU

Could it be because your .mxd is referring to a "broken" source layer (missing .gdb or unable to reach the geodatabase). In this case, it pops up a dialog : " please enter logi/password to your database " and in the case of .mxd import, -perhaps- the GUI handle isn't available to ArcGIS Pro

KeithAddison1

I had this issued with an mxd. I systematically deleted items from the mxd until it would import. The culprit was a data frame with a polygon layer, and two CAD dwg layers. I removed all its layers and it still failed to import so I assume it was something with the data frame object itself and not its layers. The data frame seemed perfectly boring as DFs go, only thing unusual about it was some annotation groups. I had also tried to copy everything into a new mxd then import the new one, to no avail.

Muensterplaner

I have the same problem:

Importing mxd to ArcGIS Pro fails. There is no clue provided as to what the reason is. I also used mxd-doctor and it says, no errors found.

There must be some real solution to it. To be honest: I would expect ESRI to provide a detailed error log to help fix the problem. We are migrating tons of mxd's here and a considerable amount of them fails to convert. It is just not possible to open every single project and delete layers one-by-one and try out when the export finally works.

So far I have seen no real solution in this forum. Given that support for arcmap ens, thousands of organisations will have this problem and there is no help.

Robert_LeClair

@Muensterplaner - I would strongly recommend you contact Esri Support Services to assist you with this workflow/item. You're correct that ArcMap support ends March 1, 2026 so 10 months from now. To date, I have not had issues importing *.mxd's into my ArcGIS Pro local install.

ttencer

I have been stacked with same problem. However i have no longer arcmap installed. How did you make this nice tree view, are you willing to share the code?:D

Robert_LeClair

Not sure if this is what the OP of the arpx tree used but there is a GitHub script located here - GitHub - fpolia21/aprx-tree-view: Convert ArcGIS Pro .aprx into interactive html mindmap - it's not an Esri product nor supported by Esri.

DEAF_PROBERT_68

When I am working on my current arcgis pro and I was thinking about this...

If you still have ArcMap and could you try export PDF with all the layers, et cetera on the map, Export the PDF and set the Layers and Attribute to set ON.

So when you open the PDF, click on the "Layers" , this feature will show you all the layers, et cetera turn on or off.

So when you are there in PDF, can you test which layers is still there or not. If there is something you don't see it there maybe there is an error when you could not import the mxd to ArcGIS Pro...

Maybe go back to MXDDoctor and delete the one that you don't see in ArcMap ?

I have not tried that but just to give you another option .

I remember I had that issues when I had a trouble import the mxd to ArcGIS Pro... I spend some time to try and fix and can't remember what it was cause it ... I thought maybe it was an Extension that I had may have deleted and left garage in ArcMap. I do not have ArcMap here anymore.

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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