NIM046650 for ArcSDE/Enterprise Geodatabase

Bug ID Number	NIM046650
Submitted	July 2, 2009
Last Modified	April 3, 2025
Applies to	ArcSDE/Enterprise Geodatabase
Version found	9.3.1
Status	Non-Reproducible

Additional Information

No Public Explanation

Workaround

Workaround from NIM001584:If workflow exists where new server and database are setup, however organization has multitudes of dedicated MXD's pointing to old server which organization wants to later re-direct. Testing has shown that if a valid dummy database connection is set up for the broken links the MXD will time-out and open with the option to repair data sources nearly as quickly as default behavior. Below are steps to reproduce described scenario:1.) Create a new SDE database over the network so it can bedisconnected from the mxd file that will be created in Step 42.) Add 3 or 4 feature classes (eg. Parcels, road centerlines,places (points))3.) Make a backup of this database (replicate the database)4.) Create an mxd file using all the feature classes created in Step25.) Save the mxd file locally and close out of it....default behavior 30 seconds6.) Remove computer from network so mxd can not access the SDEdatabase7.) Open the mxd file to see if it will hang on the invalid SDE......5-6 minutesconnections (Measure how long it takes to open the mxd)8.) Reconnect computer to network9.) Delete the feature classes from the database10.) Open the mxd file when there is a legitimate SDE connection with no data contained....45 seconds