Re: SQLCMD can't connect to SQL Server Express SP2

Suggestions:
1. You didn't specifically say that the SQL Server Browser Service was running on the SQL Server Express computer. SQL Server Express Setup configures it to start by default but who knows. Maybe the password expired or something.

2. Since your error says DBNetLib, I infer that your clients are using the SQL Server 2000 client network library. Consider upgrading them to the SQL Server 2005 "SQL Server Native Client". The SQL Server Native Client knows all about the SQL Server Browser Service which provides the connection point (ie. port number or named pipe) back to the client.

3. Since you are connecting using DBNetLib, check the Client Configuration Tools on one of the clients. What protocol is it using? You probably want TCP. Then test a connection using the connection string tcp:<computername>, <fixed port number>
If that's not working, then either the server is not listening on TCP (which really can't be the case since you set a fixed port) or maybe the IP Address can't be resolved. Try connecting to: tcp:<ipaddress>, <portnumber>
If your clients are trying to connect using named pipes, then maybe name resolution isn't working.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.


"Klerman Gutierrez" <mcs@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:%23XfHWEtXIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
Using OSQL or SQLCMD now I can connect to the SQL Server Express in the same machine where de SQL Server Express is installed, but it fails trying to connect to it from any other machine in my network.
The error message I get is:
[DBNetLib] Not valid connection
[DBNetLib]ConnectionOpen InvalidInstance()
I have SQL Server 2000 installed in another computer, and I can connect to it from any other machine including the one where the SQL Server Express is installed.
Any suggestion where to check, please ?

TVMIA,

Klerman Gutierrez




.

Relevant Pages

  • Re: Connection Error: ADO.Net and SQL Server 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... I can connect to the server through an ODBC connection ... It is very puzzling because this client doesn't seem to have anything ...
    (microsoft.public.sqlserver.connect)
  • RE: Error 17835 - When encryption and Shared Memory are enabled
    ... Did you encounter this error when you connected to your SQL Server ... Did your SQL Server instance use a certificate explicitly specified by ... you configure your client connection settings "Force Protocol Encryption" ...
    (microsoft.public.sqlserver.connect)
  • Re: Losing connections with SQL 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server automatically detects if the client falls into the sea or gets ... Does the Connection pooling mechanism do this on its ... Upgrading our app is a really big task, ...
    (microsoft.public.sqlserver.connect)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
Loading