MXD doesn't save SDE data source connections

[AlicePence]

When I add a layer from our SDE it displays fine and I can edit - but when I go to save and close the MXD then reopen it back up the data sources connections are lost (screen shot 1 below) then once I set data source it works (screen shot 2 below). 

To make it more confusing - when I open the MXD and remove the layer then re-add it back in the connection works! 

I have ArcGIS 10.6, SQL Server, and Windows 10

[George_Thompson]

Ok, update to ODBC Driver 17 reference above; Download Microsoft® ODBC Driver 17 for SQL Server® - Windows, Linux, & macOS from Official Microsoft... 

Important after installation to close the Desktop client and re-open.

[AlicePence]

I'm not sure that it's the SQL server connection since its the same native client that is installed on VM that is on our desktops - and I can access SDE just fine on the VM and on my desktop its literally when I only try to save that the connection changes on my desktop. 

[George_Thompson]

Ok, I am at a loss at this point and would recommend contacting technical support to further troubleshoot.

[AlicePence]

A new insight to this is I found out that it's only layers that are within a Feature Dataset that are causing the problem. If the feature class is not within a feature dataset I can save and open the mxd just fine.

[George_Thompson]

Based on that new information, can you please verify that you have all the correct (i.e. same) permissions to all the feature classes within the feature dataset?

If you had a mixed bag of permissions in the feature dataset, it could cause some odd behavior.

[AlicePence]

I checked the permission differences in each feature class within the feature dataset and they all have the same permissions - I also created a brand new feature dataset and then added a new feature class and still behaving the same. 

Another difference that I spotted is:

The ones that are working are; outside of a feature dataset and look like this:

GISDB.PORT.TAXLOT_PORT

The ones that are not working are (1) within a feature datastet and (2) outside of a feature dataset. but look like this:

gisdb.PORT.lease_activedoco_join

So not sure if that is causing an issue for the MXD to reset back the SQL connection are the ones that are lowercase? We have not had ran into this issue before.

[George_Thompson]

That is interesting, I am not sure. I would definitely work with Technical Support on this. Ask for a specialist on the Geodata team.

[MarinaKiriyeva]

Hello Alice,

Did you ever get an answer to your issue regarding a lost connection inside MXD?  I have the exact same problem [Windows 10, ArcGIS 10.7, SQL Server].

Thanks!

-Marina

[AlicePence]

Hi Marina - I had to install the SQL Server 2017 native client again on some users computers to get it to work. Some computers had older SQL Server native clients and i believe that is what was messing with the connection file. Once it was all cleaned up with a new 2017 native client it started behaving again 

[MarinaKiriyeva]

Thank you, Alice!  I installed SQL Client 2017 on my computer and the connections inside the MXD's started to be saved like they should.  This fix also worked for other users here.