| Bug ID Number |
NIM075759 |
| Submitted | November 28, 2011 |
| Last Modified | April 2, 2025 |
| Applies to | ArcSDE/Enterprise Geodatabase |
| Version found | 10.0 |
| Version Fixed | 10.1 |
| Status | Fixed
The bug has been fixed. See the Version Fixed and Additional Information, if applicable, for more information.
|
Description
Map documents reference hard-coded paths to ArcSDE connection files in situations where data is added via a UNC path from a shared network location. As a result, layers within map documents become unsourced if the .sde connection file is renamed or relocated.
Conversely, ArcSDE connection files that are shared via a mapped drive letter do not exhibit this behavior.
Note:
This issue has been fixed in ArcSDE 10.1 and in ArcSDE 10.0 SP5.
Cause
The method in which the ArcGIS client is referencing the .sde connection file is different for the UNC folder connection, which causes the direct path to the .sde file to be sourced.
When the path to the location of the .sde connection file is changed due to conditions such as permissions being changed or the folder having been moved, the layers within the map document become unsourced and reference the direct path of the original .sde file location.
Layer Properties of the hard coded source to the original location of .sde connection file.
![[O-Image]](https://webapps-cdn.esri.com/CDN/support-site/technical-articles-images/000011526/00N39000003LL23-0EM39000000wdLR.png)
Workaround
Use a mapped drive letter to the remote server within the ArcCatalog folder connections instead of a UNC path. This embeds the connection properties within the map document correctly instead of referencing the .sde connection file location.
Steps to Reproduce