Hello!

I have found a document that says run from command line
osql -U sa -i [password] -i instnwnd.sql

This file instnwnd.sql exist from where I execute the osql/sqlcmd command

When I do so I get this error
"C:\Program\Microsoft Visual Studio .NET
03\SDK\v1.1\Samples\Setup>osql -U sa
-P [sa] -i instnwnd.sql
[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL
Server [2].
[SQL Native Client]Login timeout expired
[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."

I can also read that osql does not support all feture of SQL Sever 2005
Use instead sqlcmd. I then tried with sqlcmd but this give this error
"C:\SQL Server 2000 Sample Databases>sqlcmd -U sa -P [sa] -i instnwnd.sql
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re 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".

I found that error HResult 0x2, Level 16, State 1
depends on TCP/IP is not enabled.
I set TCP/IP enabled and shared memory and names pipes. I have also
restarted the sql server but I
still get the same error.

Have you out there any suggestion

//Tony

try ..

sqlcmd -S SERVERNAME -E -d DBNAME -i C:\itowww.sql (windows authentication)

sqlcmd -U USERNAME -P Password -S SERVERNAME -E -d DBNAME -i C:\itowww.sql
(SQL authentication)

Thanks!

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005


"TonyJ" wrote:

A couple of things:
1. If you're connecting from a remote machine, ensure remote connections are
enabled and for the right protocols (look for remote connections in the
Surface Area Configuration tool)
2. Explicitly specify the server and instance (if appropriate) names so
you're not accidentally connecting to the wrong default instance.

Look in the SQL Server event log to see if your connection attempt even made
it to SQL Server.


joe.

"TonyJ" <johansson.andersson (AT) telia (DOT) com> wrote