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. 

[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