After getting SQL server management studio installed on desktop, getting error while trying to connect to geodatabases on SQL server 2012. ArcGIS 10.4.1 Appreciate any help!
Getting the error above after installing SQL server management studio 2016
Did you rename the database or restore the geodatabase with a different name?
The connection was working before you installed the SQL Server 2016 Management Studio?
What version is your Enterprise geodatabase?
As far as I know nothing has changed with those geodatabases.
Enterprise Geodatabase version 10.3
Yes, the connections were working before the SQL server mgmt studio 2016 was installed
Microsoft SQL Server database requirements for ArcGIS 10.3.x—Help | ArcGIS Desktop
MS SQL Server 2016 is not supported with ArcGIS 10.3.x. So maybe the installation of the SQL Server 2016 Management Studio installed some DLLs\files which is not supported with the 10.3.x gdb.
1. Uninstall Management Studio 2016 and install the 2012\2014 version if you can and then check
2. Can you upgrade the enterprise geodatabase to 10.4.1?
Will try your suggestions. Very helpful. Thank you!
Did anyone find a fix?
Unless you are using the exact same configuration as the Original Poster, I suggest you create a new Post with details of your environment.
The error occured when I renamed the database or restored it with a different name. How I can fix it if I need a different name of the database?
Thank you.
If you are using SQL Server you cannot change the name of the restored DB from the backup. You would need to restore with the original name on a new SQL Instance and then copy the data into a new SQL Server Enterprise Geodatabase with the "new" name.
I'm seeing the same error after restoring the DB from a BAK of a different DB.
DB Connection tool can see the DB but throws the error when I attempt to connect.
Did you change the name of the DB during the restore process?
no sir the DB name is the same - we restored it to a BAK from a DB with a different name, though
So you had an "empty / existing" DB then restored the .bak to that one, correct?
If so, that would cause the issue. If you restored the .bak to another DB with a different name it would break things. The only way I have seen a successful restore is to run the process and do not touch anything with the naming part.
Yessir. we restored our TEST DB (named test_mwa) using a backup of our PROD DB (named mwa).
This was an attempt to bring the 2 back into sync
Ok, that is what broke. You have to restore the test_mwa to the same name.As a test, if you restore test_mwa to the a different instance and leave the name the same, re-sync logins, can you connect then?I do know that we are looking into allowing you to change the DB name in SQL Server, not sure when it will be available. As I understand it that there will be some version restrictions with renaming it, i.e. must use versions x.x.x or newer clients (ArcGIS Pro, ArcGIS Enterprise, ArcGIS Server, etc.)
well, thanks for the info. the restore was required by a 3rd party software that runs stored procedures to update a couple of tables - that process was working fine in PROD and we wanted to replicate to give them a test environment
Has this been fixed or a work around found yet? We also restored an enterprise geodatabase with a different name for a test DEV environment and are experiencing the same issue.
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
