sqlcmd won't run - Is this a config issue?

I'm trying to use sqlcmd to execute some SQL scripts.

Using a test command with a simple query like:

sqlcmd -S HOSTNAME -d MYDATABASE -Q 'SELECT Names FROM Customers'

sqlcmd does not appear to make any attempt to connect to the server as it displays this message:

Sqlcmd: Error: Connection failure.

SQL Native Client is not installed correctly. To correct this, run SQL Server Setup.

The native client was presumably installed as part of the SQL Server setup and likely correctly. I actually get this message on any machine with SQL server installed trying to use sqlcmd so it's not a matter of the installation being corrupt.

Unfortunately the message rea开发者_StackOverflowlly tells me nothing about the problem so I don't know what the real issue is. I know the SQL Native client is working properly since a vbscript was able to execute SQL queries against the database.

Is there some additional configuration needed to use sqlcmd?

I had the same error. After a lot of searching and reinstalling, I checked my PATH for something unrelated. As the software I work on has gone through MSDE, 2005 Express and now 2008 Express R2, my PATH statement had these entries:

c:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\

I removed the 80 and 90 entries and stopped receiving the error. I tested and the install of 2005 Express still responded to the SQLCMD entry without issues.

I met this error when running the command sqlcmd. To solve this, I removed unnecessary parts of the PATH environment variable, and inserted the following:

C:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\

This PATH is for SQL Server 2012

I was also getting this error with MS SQL Server 2014.

Sqlcmd: Error: Connection failure. SQL Native Client is not installed correctly. To correct this, run SQL Server Setup.

First, confirm that SQL Server Native Client is installed. As specified on MSDN, the bcp.exe and SQLCMD.exe files should be located in the below directory.

<Install Directory>\Client SDK\ODBC\110\Tools\Binn

If the files are not there, you can download and install the the client from the Microsoft Download center, using either ENU\x86\sqlncli.msi or ENU\x64\sqlncli.msi. MSSQL 2014 uses the 2012 client

Once this is done, you should be able to use SQLCMD without issues.

Path environment variable on my machine contains the following entries:

C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn
C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\
C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\
C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\

I know the SQL Native client is working properly since a vbscript was able to execute SQL queries against the database.

No you don't. You only know that SOME client works, but not necessarily the SQL Native client.

All roads lead to Rome http://www.connectionstrings.com/sql-server-2008 (check Provider list), but one happens to be blocked.

Just perform a repair/modify setup from Control Panel, or install another instance (making sure Native client is installed), then remove it again.