Latest Contributions by 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  ... View more

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. ... View more

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. ... View more

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.  ... View more

I have Microsoft SQL Server 2012 Native Client installed on my machine - it's the same that is on the VM machine that is where the MXD is working ... View more

Re-installing ArcMap did not help. Also sorry about the confusion, but I just received more information from our team that our SQL server is NOT highly available for both our test and prod environments. Also, I tried saving an ArcScene map (realize that ArcScene does not save as a MXD) but it worked when I saved and reopened again. So not sure why it's only for MXDs that the connections change. ... View more

Another test that I just ran too is the MXD Doctor and I can see all the connections and the layers just fine in the viewer - but when I open the MXD the connections are lost. So I'll try to uninstall and reinstall ArcMap and see if that clears it up. ... View more

What is interesting about the SDE connection is that when I open a MXD on my VM (the VM has the SQL server) everything works just fine- where I can save the MXD and the connections are not lost when I open it back up. It's only when I try to save a MXD on my personal machine that this is happening. Not sure why all of a sudden that local machines are reverting back this old 'old school ArcSDE'?  I tried the rebuild and that still didn't work either, and our SQL Server is highly available. ... View more

Hi George - we are using SQL Server 2017 and not sure where to find if it's highly available. also when you say 'delete the .sde connection file and recreate it' are you saying delete it from catalog and add it back or create a whole new .sde file? ... View more

So after following your links i was able to see that if I use the 'Create Database View' tool and just straight up make a view called "mv_ELEC_VAULT" that trigger (created way before my time...) ended up working!! No need to figure out how to use the SDE Command Line tools -  Again, thanks for your insight and I was able to get the issue resolved. Now off to making all these new views. ... View more

I think we are getting closer now to figuring out the issue and it's those MV tables that -like you said- need to be created with the SDE command-line tools. I'm meeting with my team here soon to find if there is extra documentation somewhere about creating those and if we get stuck again - I'll gladly take that Tech Supports help. Thanks for the bit of insight of the issue so far! ... View more

I've looked in Table and Views in SQL server have not been able to find that port.mv_ELEC_VAULT - either its really good at hiding or it no longer exists (I fear the latter). I've found past documents on our GIS DB creation showing that MV tables are required, so not sure how those are set up ie different than the versioned tables that end in "_evw" ... View more

I was wondering if that "mv_" was related to a multi-versioned view created before. I tried your step and the Enable SQL Access option is greyed out and I'm the dataowner ... View more