Client machine having difficulty opening MXD's on shared drive?

Anonymous User

Original User: se2539

Got a call from a colleague that a client machine was having difficulty accessing saved MXD's on a shared network drive.  The machine could open the MXD's no problem, but would experience the dreaded red exclamation points for all the feature classes and tables that are located on the enterprise GDB. Right clicking and looking at the data source, something weird was definitely going on:

[ATTACH=CONFIG]30881[/ATTACH]

Note the ALL CAPS ... never seen that before when looking at the data source of an FC or Table.

Funny thing is, when one manually resets the data source (right click the FC/Table, goes to properties, "Set Data Source"), the layer works just fine. 



Here's a look at what a "working" feature class should look like when accessing from our database:

[ATTACH=CONFIG]30882[/ATTACH]

I should note that this is only occurring on only one client machine in an organization of about 7 or so machines.  Additionally, I should also point out that this organization received a CPU upgrade and software upgrade to ArcGIS 10.1 around the September 2013 time frame ... however, this particular problem has only occurred in the last week or so on the one machine in question.



This problem has really got me and my colleagues stumped ... we would really like to be able to open MXD's without having to repair every single path!

Bad.png

Good.png

Anonymous User

Original User: mvolz47

If I had performed the operation in v10.0, it would have used v10.0 SDE connections which are different from v10.1-10.2 SDE connections.  One difference is that versions other than Default are not accessible in v10.2 if I am still using v10.0 SDE connections.  If I convert these v10.0 connections to v10.2 connections, then all versions are accessible in v10.2.

The ramifications of this problem would not be visible to most SDE users who only have view privileges to the Default version.  This is more problemmatic for SDE editors who make their edits in their own specific versions of SDE so they would never be able to create or access these versions.