NIM038965 : Slow opening of MXDs due to old connection information

1549
5
09-12-2016 03:37 PM
TodStevens
New Contributor II

Does anyone have a workaround for this 2008 defect? I have tried all the proposed python and mxddoctor solutions without luck. Inserting entries into the hosts file for old server (actually a server in a different domain) works but is not allowed in the government production environment.

The MXD still contains old arcgis connection information and thus when opening the MXD you suffer a delay of up to 50 seconds.

Many Thanks.

Synopsis

Map documents (MXDs) preserve the layers' old server information after resetting the data source, which causes slowness in opening the documents if the older server is taken off the network.

0 Kudos
5 Replies
DanPatterson_Retired
MVP Emeritus

That NIM doesn't show up on support Esri Support Search-Results  using any incarnation of searches.  Do you haver a direct link?  Perhaps because of the 2008 date, other workarounds have been provided, or legacy projects require an upgrade.  Since it is government, I would be surprised that a solution hasn't been proposed, even if it wasn't acceptable to your IT department.

0 Kudos
TodStevens
New Contributor II

Hi Dan

http://support.esri.com/bugs/nimbus/TklNMDM4OTY1

Regards

Tod

0 Kudos
DanPatterson_Retired
MVP Emeritus

I think ... Not in Current Product Plan ... indicates the status, probably because it affects only a few.  I would recommend contacting tech support to see if any alternates to the alternative solution have been reported by others.  I am also not sure what ... No Public Explanation... means, perhaps there are some disclosure issues around it.  good luck

0 Kudos
ChristianWells
Esri Regular Contributor

One workaround we have seen to work is to re-generate the MXD's via Python. You could try the following script here:

developer-support/refresh-mxd-layers.py at gh-pages · Esri/developer-support · GitHub 

This will take a folder of MXDs, move them to a blank MXD and then save to a new folder. 

It could be worth a test on a handful of MXDs

JayantaPoddar
MVP Esteemed Contributor

You could try disconnecting the client from Network > Open the MXD (Is it opening faster?) > Connect to the Network > Repair the Data Source.



Think Location
0 Kudos