Cannot connect with SQLCMD - VIA Provider : The specified module could not be found

I have the full version of SQL Server 2005 on my machine under XP. Installed ok and can connect with management studio, but if I try and connect with Analysis Services or even SQLCMD, I get the error below :

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 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 have networking enabled, I've enabled all the protocols (apart from VIA because it doesn't start if you do that), and I have all the services running.

Any ideas what can be up ?

I have now fixed this issue and thought I'd just list what was wrong :

The VIA message was because in desperation to connect I had enabled some VIA connections - I think client side.

I disabled all connection types for both client and server except shared memory and TCP/IP.

Still didn't work - and gave a message that the server refused connection.

I then looked at the server side TCP options and found the port number, using SQLCMD tcp:servername,portnumber I could now connect !!

Finally changed the client side TCP to use this port number and now can connect with SQLCMD and no options.

My main gripe is why didn't it all work as installed and why did I have to go through all this to get it to connect !!!

Cannot connect to SQL Express Remotely

I have SQL Express April CTP (from VS Beta 2) installed on machineA, but I cannot connect to it from machineB using the command "sqlcmd -S machineA\sqlexpress -E". This command works just fine from machineA.

I have enabled the TCP/IP protocol for the SQLExpress instance through the configuration manager, and turned off the Windows Firewall on machineA.

Any ideas on what I'm doing wrong?

Hi Michael,

By default network protocols (TCP/IP, named pipe) are disabled for SQL Server Express Editions.

You can use SQL Server configuration manager tool to Enable the server protocols on which the instance of SQL Server will listen.

hope this is helpful...

thanks..
Rajesh|||Does this help:

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx|||Thanks Euan -- That did the trick!|||Hi,

I have the same problem, I cannot connect remotely to sql server express

I have done all the steps in that article http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

but still not working remotely although locally is ok

I have tried also on domain lan and on workgroup lan

On domain, on different client computers with different domain users I received different error messages:

...login failed for user. the user is not asociated with a trusted sql server conenction...
or
...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 ... error locating server..
or
...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 ... login failed...

I am connectiong to my_machine\SQLEXPRESS with windows authentication, same as on the server machine

I cannot figure out what should be the problem, any help would be apreciated.

Thank you for your time.
Corina

Cannot connect to SQL Express Remotely

I have SQL Express April CTP (from VS Beta 2) installed on machineA, but I cannot connect to it from machineB using the command "sqlcmd -S machineA\sqlexpress -E". This command works just fine from machineA.

I have enabled the TCP/IP protocol for the SQLExpress instance through the configuration manager, and turned off the Windows Firewall on machineA.

Any ideas on what I'm doing wrong?

Hi Michael,

By default network protocols (TCP/IP, named pipe) are disabled for SQL Server Express Editions.

You can use SQL Server configuration manager tool to Enable the server protocols on which the instance of SQL Server will listen.

hope this is helpful...

thanks..
Rajesh|||Does this help:

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx|||Thanks Euan -- That did the trick!|||Hi,

I have the same problem, I cannot connect remotely to sql server express

I have done all the steps in that article http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

but still not working remotely although locally is ok

I have tried also on domain lan and on workgroup lan

On domain, on different client computers with different domain users I received different error messages:

...login failed for user. the user is not asociated with a trusted sql server conenction...
or
...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 ... error locating server..
or
...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 ... login failed...

I am connectiong to my_machine\SQLEXPRESS with windows authentication, same as on the server machine

I cannot figure out what should be the problem, any help would be apreciated.

Thank you for your time.
Corina

cannot connect to sql 2005 from isql

I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
server, I can use sqlcmd to connect to the database. However, I failed
to connect to the database from a client machine using sql7's isql. The
error was
DB-Library: Unable to connect: SQL Server is unavailable or does not
exist.
Net-Library error 1326: ConnectionOpen (CreateFile()).
Please advise, thanks.Is the server instance listening to Named Pipes?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AH" <hhhsu7a@.yahoo.com> wrote in message
news:1167102465.643393.154420@.73g2000cwn.googlegroups.com...
>I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> server, I can use sqlcmd to connect to the database. However, I failed
> to connect to the database from a client machine using sql7's isql. The
> error was
> DB-Library: Unable to connect: SQL Server is unavailable or does not
> exist.
> Net-Library error 1326: ConnectionOpen (CreateFile()).
> Please advise, thanks.
>|||Hi
If this is SQL Express then network protocols are disabled by default. Check
which network protocols are being used, if necessary you may wish to create
an alias on the client to use TCP/IP to connect to the instance. Also make
sure that the client machine has the latest service packs.
John
"AH" wrote:
> I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> server, I can use sqlcmd to connect to the database. However, I failed
> to connect to the database from a client machine using sql7's isql. The
> error was
> DB-Library: Unable to connect: SQL Server is unavailable or does not
> exist.
> Net-Library error 1326: ConnectionOpen (CreateFile()).
> Please advise, thanks.
>|||John,
I tried to open TCP on the server but still got the same error when
connecting from client machine. The client has SQL 7 SP2. Do I need to
go to SP 4?
Does Microsoft provide any tool to trace the connection?
Thanks,
Andy
John Bell wrote:
> Hi
> If this is SQL Express then network protocols are disabled by default. Check
> which network protocols are being used, if necessary you may wish to create
> an alias on the client to use TCP/IP to connect to the instance. Also make
> sure that the client machine has the latest service packs.
> John
>
> "AH" wrote:
> > I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> > server, I can use sqlcmd to connect to the database. However, I failed
> > to connect to the database from a client machine using sql7's isql. The
> > error was
> > DB-Library: Unable to connect: SQL Server is unavailable or does not
> > exist.
> > Net-Library error 1326: ConnectionOpen (CreateFile()).
> >
> > Please advise, thanks.
> >
> >

Cannot connect to Remote SQL Server Named Instance

Hi...
On a remote server, I have SQL 2005 installed as the default instance as
well as a new named instance.
From SQLCMD, I can connect to both instances. However, from Management
Studio, I can only connect to the default instance. Is there something
special I have to do to connect to the named instance? I try connecting
using:
[My-Server-Name]/InstanceName
Any ideas? I get the "error locating server/instance specified" generic
error.
Thanks![/] is also not allowed for a servername -the instance is part of the na
me.
So put the square brackets around the entire [server/instance] name.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Forch" <Forch@.discussions.microsoft.com> wrote in message
news:DE18DCC1-CA47-4066-8E34-2ED8250A9DD5@.microsoft.com...
> Hi...
> On a remote server, I have SQL 2005 installed as the default instance as
> well as a new named instance.
> From SQLCMD, I can connect to both instances. However, from Management
> Studio, I can only connect to the default instance. Is there something
> special I have to do to connect to the named instance? I try connecting
> using:
> [My-Server-Name]/InstanceName
> Any ideas? I get the "error locating server/instance specified" generic
> error.
> Thanks!|||Use SQL Server Configuration Manager and for the Services,
make sure the SQL Browser Service is running.
-Sue
On Thu, 10 Aug 2006 09:06:01 -0700, Forch
<Forch@.discussions.microsoft.com> wrote:

>Hi...
>On a remote server, I have SQL 2005 installed as the default instance as
>well as a new named instance.
>From SQLCMD, I can connect to both instances. However, from Management
>Studio, I can only connect to the default instance. Is there something
>special I have to do to connect to the named instance? I try connecting
>using:
>[My-Server-Name]/InstanceName
>Any ideas? I get the "error locating server/instance specified" generic
>error.
>Thanks!|||Thanks for the suggestion. Unfortunately it didn't work...
The name without the square brackets works with Management Studio locally.
Do you have any other ideas?
Thanks,
Mark
"Arnie Rowland" wrote:

> [/] is also not allowed for a servername -the instance is part of the
name.
> So put the square brackets around the entire [server/instance] name.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Forch" <Forch@.discussions.microsoft.com> wrote in message
> news:DE18DCC1-CA47-4066-8E34-2ED8250A9DD5@.microsoft.com...
>
>