ArcGIS 10.1, SP1, Build 3143
ArcGIS Server 10.1
I installed ArcGIS on several new computers in a training lab for our county, I also installed all the SP's, patches and SQL Native Client files. This is the same installation as my desktop. When I log in to this computer with my existing username and password, go to ArcCatalog and try to set up a connection to SDE, I get the following error.
Does anyone have any suggestions?
Thanks,
Chad
Solved! Go to Solution.
On a machine with good connections to SDE browse to: C:\Users\<your user>\AppData\Roaming\ESRI\Desktop10.2\ArcCatalog. You may have to unhide the folder: Show hidden files - Windows Help
Copy anything with a .sde and paste it to the same folder on the new machine.
Can you provide us a screenshot of the Connection properties?
I have also tried using the Database Authentication but get the same error.
Can you login using that user in SQL Server management Studio?
The Windows Authenticated login being used to make that connection-- does it have a default database assigned within SQL Server?
Also check the Direct_connect log on the problematic machine, it may provide some more information.
Usual location of that log: C:\Users\user_name\AppData\Local\Temp\sdedc_SQL Server.log
Yes I can.
No it doesn't
Here is the latest log entry in that file:
IDBInitialize::Initialize Failed
DB_instance_open() db_connect error: 4064
CAN'T OPEN INSTANCE: sde:sqlserver.
Spatial Engine Connection Failed (-51).
Cannot Get Access to Instance sde:sqlserver
Can you assign that login a Default database and then try again.
I cannot assign the user a default database due to permissions. Although the user I am using with Database Authentication does have a default database associated with that account.
IDBInitialize::Initialize Failed
DB_instance_open() db_connect error: 4064
CAN'T OPEN INSTANCE: sde:sqlserver.
Spatial Engine Connection Failed (-51).
Cannot Get Access to Instance sde:sqlserver
Error log report
You do realize that on my existing desktop computer, I have already connected to SDE multiple times. This issue is with a new computer in a training lab on the same network with the same login.