topic Re: Failure to access the DBMS server in Data Management Questions

Failure to access the DBMS server

CynthiaWanschura — Thu, 03 Jan 2013 17:26:26 GMT

I�??m getting a �??Failure to access the DBMS server�?� error when I try to create an ArcSDE geodatabase in ArcCatalog 10.1. Someone else had a similar problem:
http://forums.arcgis.com/threads/66442-Cannot-Connect-to-SQL?highlight=Failure+access+DBMS+server

I�??ve tried everything mentioned in that forum but I�??m still having trouble. Here�??s my setup:

Installed on my 64-bit Windows Server 2008 Server:
- Microsoft SQL Server 2008 R2 (64-bit)
- ArcSDE 10.1 for Microsoft SQL Server
- ArcGIS 10.1 SP1 for Server - Enterprise (Advanced)

Installed on my 64-bit Windows 7 Desktop:
- ArcGIS 10.1 SP1 for Desktop - Advanced (ArcInfo)
- Microsoft SQL Server 2008 Native Client

The installation of ArcGIS Server was a completely clean installation; no version of ArcGIS Server had been on the server prior. When I recently upgraded a server that had ArcGIS Server 10.0 on it prior, I encountered no trouble. It makes me think there was a SQL or Windows setting that I changed long ago in 10.0 that carries through but I can�??t think what. I�??m an administrator both in Windows and in SQL.

I would greatly appreciate help so I can stop banging my head against the wall. 🙂

Thank you!

Re: Failure to access the DBMS server

VinceAngelo — Thu, 03 Jan 2013 17:37:40 GMT

Did you install the 32-bit native client or the 64? ArcGIS Desktop is a 32-bit application.

- V

Re: Failure to access the DBMS server

CynthiaWanschura — Thu, 03 Jan 2013 19:04:25 GMT

It was already installed so I'm not sure. How do I find that information? There's nothing to indicate it as 64-bit in the Programs and Features list in Control Panel. I am able to access another server running ArcGIS Server 10.1 without an issue, so I assume that the Microsoft SQL Server 2008 Native Client I have on my desktop is compatible with ArcGIS Desktop. That could be a faulty assumption.

Thank you for responding!

Re: Failure to access the DBMS server

VinceAngelo — Thu, 03 Jan 2013 19:23:04 GMT

ArcGIS Server 10.1 is a 64-bit app -- It requires the 64-bit Native client. The fact that
your old server (where the 32-bit client had been installed for 32-bit AGS 10.0) works
indicates that a missing 32-bit native client could be the issue.

- V

Re: Failure to access the DBMS server

MarcoBoeringa — Thu, 03 Jan 2013 19:52:29 GMT

It was already installed so I'm not sure. How do I find that information? There's nothing to indicate it as 64-bit in the Programs and Features list in Control Panel. I am able to access another server running ArcGIS Server 10.1 without an issue, so I assume that the Microsoft SQL Server 2008 Native Client I have on my desktop is compatible with ArcGIS Desktop. That could be a faulty assumption.

You may try to use the "SQL Server" ODBC driver instead of the "SQL Server Native Client X.X" too, at least if Microsoft has documented it to be able to connect to your SQL Server version, otherwise it won't be of use. However, I can't find it now, but I think I saw a recent thread where someone reported solving his specific issues regarding driver issues by choosing the non-"Native Client" older driver.

I also recommend you to have a look at this thread by myself, regarding a Windows 7 ODBC driver issue I had. I don't know if it is a general issue and if it is related to your issues, but it will at least help you find out if you run the 32- or 64-bit driver:

http://forums.arcgis.com/threads/70820-BIG-TIP-for-ArcGIS-ODBC-OLEDB-users-on-64-bit-Windows

Re: Failure to access the DBMS server: Is it Windows Firewall?

SpencerSimpson — Fri, 04 Jan 2013 14:49:56 GMT

The first thing you should check is Windows Firewall.

By default, Windows Server 2008 enables Windows Firewall, and blocks all incoming connections except those that have a rule allowing something.

Windows does not create a rule for SQL Server and it does not have a stock rule that you can simply "turn on".

Furthermore, the SQL Server installer (which would be the logical place to have a rule automatically created) does not create a rule for you when you create a SQL Server instance.

In order for remote computers (i.e. anything other than the OS running the SQL Server instance) to accept SQL Server connections you need to add an Incoming traffic rule for the port (tcp port 1433 by default) the instance is running on. OR turn Windows Firewall off completely.

Re: Failure to access the DBMS server

CynthiaWanschura — Fri, 04 Jan 2013 16:28:36 GMT

ArcGIS Server 10.1 is a 64-bit app -- It requires the 64-bit Native client. The fact that
your old server (where the 32-bit client had been installed for 32-bit AGS 10.0) works
indicates that a missing 32-bit native client could be the issue.

- V

I need a little clarification. Am I supposed to install the 32-bit Native Client on my computer or the server?

Thank you!

Re: Failure to access the DBMS server

VinceAngelo — Fri, 04 Jan 2013 17:20:31 GMT

32-bit client goes where the 32-bit software is run. If ArcGIS Desktop is local, then local.

- V

Re: Failure to access the DBMS server

CynthiaWanschura — Fri, 04 Jan 2013 18:24:38 GMT

That's what I thought but I'm getting an error that is preventing me from installing the 32-bit Native Client on my computer, "Installation of this product failed because it is not supported on this operating system. For Information on supported configurations, see the product documentation." I thought perhaps I was mistaken. Any recommendations? Thanks!

Re: Failure to access the DBMS server

ThomasDunn — Mon, 07 Jan 2013 15:52:15 GMT

When you install the 32-bit SQL Native client, you get only the 32-bit client. It is the DLL loaded by 32-bit applications like ArcGIS Desktop. The 32-bit installer is meant for use with 32-bit Windows only.

When you install the 64-bit SQL Native Client, you get both the 64-bit and the 32-bit client. This allows either 64-bit or 32-bit applications to load the appropriate DLL. You should install the 64-bit client on 64-bit Windows because 64-bit Windows can host both 64-bit and 32-bit applications.

Re: Failure to access the DBMS server

ShannonShields — Mon, 07 Jan 2013 16:19:48 GMT

You choose the SQL Server Native Client based on your OS. If it is a 64-bit OS, you must install the 64-bit client. As Tom says, the 64-bit client contains both 32-bit and 64-bit components. Even though ArcGIS Desktop is a 32-bit application, you'll still install the 64-bit Native Client.

-Shannon

Re: Failure to access the DBMS server

CynthiaWanschura — Mon, 07 Jan 2013 17:31:46 GMT

The 64-bit installation of Native Client is already installed. Is there another likely culprit? I can access the server through Windows just fine. I can also access the SDE features from ArcGIS Desktop installed on the server itself. However, I still get the error "Failure to access the DBMS server" when I try to run SDE features from ArcCatalog on my Desktop.

Thank you for the help!

Re: Failure to access the DBMS server

ThomasDunn — Mon, 07 Jan 2013 17:55:12 GMT

First, use SQL Server Configuration Manager to make sure that connections are supported over TCP/IP. Documentation for this is found at http://msdn.microsoft.com/en-US/library/ms174212(v=sql.105).aspx

The next thing is to check basic connectivity. You mentioned that you can access the server through Windows, so let's assume that it is not an address resolution problem or a basic network problem.

If you have SQL Server Management Studio installed on the client, you can try using that to connect to SQL Server on the remote server. This will test whether the SQL Native Client is installed, whether the port is open on the client firewall, and whether your connection credentials are correct. You can download SSMS from Microsoft.

If you don't have SSMS installed and do not want to download and install it, you can check connectivity with a tool available from Codeplex named the Port Ping Utility, or portping.exe. You can find it at http://portping.codeplex.com/. Enter the server name and the port number (1433). If the server is alive and accepting connections, you will see:

Attempting to resolve myservername to an address
myservername resolved to nnn.nnn.nnn.nnn in 0 milliseconds
Success! Pinged port 1433 in 16 milliseconds

If the server exists but SQL Server is not running on the port, you will see:

Attempting to resolve myservername to an address
myservername resolved to nnn.nnn.nnn.nnn in 15 milliseconds
Error Detected: Connection refused (10061) returned.

If the server is unreachable, you will see:

Attempting to resolve myservername to an address
Error detected: Host not found (11001)
Failed to ping port!

Re: Failure to access the DBMS server

deleted-user-yFo_UoWEJbkc — Wed, 20 Apr 2016 23:21:48 GMT

Just want to confirm that this solution is what worked for us. We had our IT turn off the firewall on the server that is hosting our new SQL instance, and vi-oh-lay, the tool ran just fine. We narrowed it down to this as the probable source of the error by attempting to connect to the new SQL instance using Management Studio on a local machine (i.e. not on/within the server itself), and the attempt failed, so that more or less confirmed that "access" to the server was limited. Anyhow, thanks for the tip to help us narrow it down!