Re: sql setup error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

It looks like your client is trying to connect with the VIA protocol for
some reason. Use the SQL Server Configuration manager to ensure that the
via protocol is disabled on both the client and the server. I assume you
are running sqlcmd on the same machine as SQL Express.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"rbarr8" <rbarr8@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0CDF5F85-AFCE-48F5-ABC7-C14C3E51D73D@xxxxxxxxxxxxxxxx
I am trying to work through the visual C# step by step book and it requires
visual sql 2005 express to be running on my machine. I show it running but
when I type the code from the book "sqlcmd -s roger-xp-x2\SQLExpress -E"
(without the quotes) I get the following error: HResult 0x7E, Level 16,
State 1 VIA Provider: The specified module could not be found. Sqlcmd:
Error: Microsoft SQL Native Client : An error has occurred while
establishing
a connection to the server. When connecting to SQL Server 2005, this
failure
may be caused by the fact that under the default settings SQL Server does
not
allow remote connections. Sqlcmd: Error: Microsoft SQL Native Client :
Login
timeout expired.

Any ideas where I might look to clear this error?

Thanks, Roger


.

Relevant Pages

  • Re: connect to named instance w/ non-default port
    ... SQL Native Client Configuration. ... An error has occurred while establishing a connection to the server. ... under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.sqlserver.connect)
  • Source table filtering in DTS by target table values.
    ... I am new to SQL Server and to DTs. ... for the client master. ... file (created in the DTS package) and add them batch by batch ...
    (microsoft.public.sqlserver.dts)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Database Server based on SQL database
    ... SQL is a language, not a protocol - they are two different things. ... TDS originated with Sybase and is used by SQL Server (earlier versions were ... both the client and the server side. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Fix of problem connecting VS2005 to remote Sql 2000 server
    ... Make sure your SQL server is listening on port 1433, that is, on service ... you need to make sure you connect to the SQL server using the ... In the "SQL Native Client Configuration", select Client Protocol and make ...
    (microsoft.public.dotnet.languages.csharp)