@@eGISAssociates I would have the map sit there at importing for a good amount of time and then it would just stop with a generic error. I ended out fixing the problem by doing analyze map and going through the errors. I had done it before but there was a spatial index error for a raster data set that I had that would never generate a spatial index. Once I took that layer out the map would import.
@@JeremyZimmerman It is always good to analyze your map and data before importing. MXD files have a nasty habit of becoming slowly corrupted over time. So while they may still open in ArcMap, they will start to run slow and have other issues. ArcGIS Desktop comes with two utilities which you can use to help keep your MXDs healthy, MXD Doctor and Document Defragger. The MXD Doctor is typically used on an MXD which is already having issues. The Document Defragger is good to use on an MXD you use often and regularly make changes too.
