pmf file containing direct connection links to an ArcSDE SQL Server database.
Once the SQL Server Native Client has been installed, proceed with establishing an ArcSDE direct connection or open an existing.
By deploying the setup.exe, the Microsoft SQL Server Native Client setup is included in the installation.ĭo not execute the setup.msi as this does not install any prerequisite checks.įor additional information please review the following link: Execute the ArcGIS Desktop setup.exe - Application.If however, the SQL Server 2008 Native Client has not been installed, then proceed to step 3. If the SQL Server 2008 Native Client has already been installed, then do not proceed to step 3 as this may not be the cause of the specific connection issues. Check to see if the Microsoft SQL Server 2008 Native Client has been installed.
On the Windows client machine, in Add / Remove Programs, verify that 'Turn Windows features on or off' has been selected.Please verify that the following steps have been completed. This can optionally be installed with ArcGIS Engine.ĭepending on the options chosen during installation, the Microsoft SQL Server Native Client (SNaC) may not have been installed. pmf file using an ArcSDE direct connection.īeginning with ArcGIS 10, the SQL Server Native Client 2008, a prerequisite to making direct connections to SQL Server, is installed with ArcGIS Desktop, ArcGIS Server, and ArcReader. One possibility for this behavior could be that the Microsoft SQL Server Native Client is not installed on the client machine(s) attempting to connect to an ArcSDE database, or open an existing. pmf files where the data sources are broken.
Instructions provided describe how to ensure that Microsoft SQL Server Native Client (SNaC) is installed on ArcGIS Desktop products.Įven when ArcGIS Desktop software has been successfully installed, there can be issues establishing a direct connection to an ArcSDE database or upon opening existing. Use the test button at the end to confirm you have a connection.How To: Ensure that the Microsoft SQL Server Native Client is installed with the ArcGIS Desktop products Summary
The driver will prompt you for connection information. You are able to create a connection from the Microsoft ODBC Data Source Administrator to SQL Server working locally on the server.ĭo this by creating a System DSN for the driver you have installed. This is especially true of the machine address IP (not just localhost 127.0.0.1). You will need to make sure that the various IPV4 and the IPV6 ports are both Active and Enabled. There is a separate tab labeled IP Addresses. On the Protocol tab, make sure Enabled is set to Yes and Listen All is set to YesĦ. Select the Protocols for SQLEXPRESS item, or whatever name is appropriate for the instance you are configuring.ĥ. Again, you want to make changes to the 32-bit configuration.Ģ. Select SQL Server Network Configuration (32bit). There will be a single dialog showing the port this should default to 1433, but you may want to check it.ġ.
Double-click on the item to open the properties dialog.ĥ. Make sure TCP/IP is enabled (you can right-click on the item to enable it).Ĥ. Again, you want to make changes to the 32-bit configuration.ģ. Select SQL Native Client 10.0 Configuration (32bit) (for SQL Server 2008). Finally, select SQL Server Configuration Manager. Microsoft SQL Server Native Client software - Installing Microsofts Native Client software automatically installs a newer driver, SQLNCLI10 or SQLNCLI11. From there, choose Computer Management and open the item in the tree labeled Services and Applications.
Select the Administrative Tools option on the Windows Control Panel.Ģ. I suspect that Microsoft sets it up for local use deliberately.ġ. Make sure that TCP/IP is enabled as a protocol on both the client and the server machines. SQL Server 2008 - Native Client version 10 SQL Server 2005 - Native Client version 9 SQL Server 2000 - MDAC (the classic ODBC driver) Previously, updating the MDAC (Microsoft Data Access Components) package kept things current.
Note that there are three different drivers from Microsoft. The Microsoft ODBC driver for SQL Server is installed on the machine where Alpha Anywhere is running. Please confirm that the following are in place: You can use SQL Server Configuration Manager or SQL Server Management Studio to browse your instances. The instance name you use in your connection string must match the instance name of the server.