.NET 2.0/SQL 2000 Named Pipes Provider, error: 40

I have an app that I've written in .NET 2.0 using SQL 2000 as the back end. It works fine in development but when I move it out to our QA server I get the following error.

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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

One of the odd things I notice is that the error message references SQL Server 2005 when that's not installed on our QA box, only SQL 2000 is on it.

I've checked the server and TCP/IP and Named Pipes are enabled.

Here is my connection string

<add name="myConnectionString" connectionString="Data Source=(local);Integrated Security=false;Initial Catalog=TestDatabase;User Id=myUsername;Password=myPassword;" providerName="System.Data.SqlClient"/>

There's at least one other .NET 2.0 application running on this server that accesses the database so I know that it can work! However, have access to the source code for that application so it's not any help with my troubleshooting.

Any thoughts or ideas?

Is the SqlServer 2000 service running on the same machine? You connection configuration is pointed to a (local) copy of SqlServer. Also, make sure that the myUsername exists on the QA server.

|||

Yes. Sql 2000 is on the same box.

And I double checked that myUsername exists in that QA SQL server and has rights to my database.

Thanks though.

I'll post back when I figure it out.

If anyone else wants to weigh in I'm all ears.

|||

Hi,

I had the same problem.

Check this Registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo.

Are there any entries that reference the SQL server you want to use (DBMPNTW = named pipes)? If so remove them.

Regards,

Thierry

.BAK extension ?

Hi !
Usualy I do not use SQL server, but this time I have got some data to
import. Data is on the CD, and it is named with extension .BAK. The
organization I've got data from does not have true DBA at this moment,
and I am not sure what I actualy got. The previous DBA resigned. I have
requested dump of database structure only, but I could manage with full
database dump, too. I am afraid that the file I've got is not either of
those two.
Currently I do not have SQL server installed.
Could .BAK files be interchanged between different machines ?
Could .BAK be an incremental backup ?
Are they compatibile for different versions of SQL server ?
Person that gave me the CD was not able to tell what version of SQL
server are they running.
DG.BAK is the standard extension for a full backup. You'll have to have a
recent version of SQL Server to try and restore it. If it restores OK, you
can extract the structure in the form of a script.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Drazen Gemic" <anyone@.anywhere.tk> wrote in message
news:dv7haf$me7$1@.magcargo.vodatel.hr...
Hi !
Usualy I do not use SQL server, but this time I have got some data to
import. Data is on the CD, and it is named with extension .BAK. The
organization I've got data from does not have true DBA at this moment,
and I am not sure what I actualy got. The previous DBA resigned. I have
requested dump of database structure only, but I could manage with full
database dump, too. I am afraid that the file I've got is not either of
those two.
Currently I do not have SQL server installed.
Could .BAK files be interchanged between different machines ?
Could .BAK be an incremental backup ?
Are they compatibile for different versions of SQL server ?
Person that gave me the CD was not able to tell what version of SQL
server are they running.
DG

.BAK extension ?

Hi !
Usualy I do not use SQL server, but this time I have got some data to
import. Data is on the CD, and it is named with extension .BAK. The
organization I've got data from does not have true DBA at this moment,
and I am not sure what I actualy got. The previous DBA resigned. I have
requested dump of database structure only, but I could manage with full
database dump, too. I am afraid that the file I've got is not either of
those two.
Currently I do not have SQL server installed.
Could .BAK files be interchanged between different machines ?
Could .BAK be an incremental backup ?
Are they compatibile for different versions of SQL server ?
Person that gave me the CD was not able to tell what version of SQL
server are they running.
DG.BAK is the standard extension for a full backup. You'll have to have a
recent version of SQL Server to try and restore it. If it restores OK, you
can extract the structure in the form of a script.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Drazen Gemic" <anyone@.anywhere.tk> wrote in message
news:dv7haf$me7$1@.magcargo.vodatel.hr...
Hi !
Usualy I do not use SQL server, but this time I have got some data to
import. Data is on the CD, and it is named with extension .BAK. The
organization I've got data from does not have true DBA at this moment,
and I am not sure what I actualy got. The previous DBA resigned. I have
requested dump of database structure only, but I could manage with full
database dump, too. I am afraid that the file I've got is not either of
those two.
Currently I do not have SQL server installed.
Could .BAK files be interchanged between different machines ?
Could .BAK be an incremental backup ?
Are they compatibile for different versions of SQL server ?
Person that gave me the CD was not able to tell what version of SQL
server are they running.
DG

.BAK extension ?

Hi !
Usualy I do not use SQL server, but this time I have got some data to
import. Data is on the CD, and it is named with extension .BAK. The
organization I've got data from does not have true DBA at this moment,
and I am not sure what I actualy got. The previous DBA resigned. I have
requested dump of database structure only, but I could manage with full
database dump, too. I am afraid that the file I've got is not either of
those two.
Currently I do not have SQL server installed.
Could .BAK files be interchanged between different machines ?
Could .BAK be an incremental backup ?
Are they compatibile for different versions of SQL server ?
Person that gave me the CD was not able to tell what version of SQL
server are they running.
DG
..BAK is the standard extension for a full backup. You'll have to have a
recent version of SQL Server to try and restore it. If it restores OK, you
can extract the structure in the form of a script.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Drazen Gemic" <anyone@.anywhere.tk> wrote in message
news:dv7haf$me7$1@.magcargo.vodatel.hr...
Hi !
Usualy I do not use SQL server, but this time I have got some data to
import. Data is on the CD, and it is named with extension .BAK. The
organization I've got data from does not have true DBA at this moment,
and I am not sure what I actualy got. The previous DBA resigned. I have
requested dump of database structure only, but I could manage with full
database dump, too. I am afraid that the file I've got is not either of
those two.
Currently I do not have SQL server installed.
Could .BAK files be interchanged between different machines ?
Could .BAK be an incremental backup ?
Are they compatibile for different versions of SQL server ?
Person that gave me the CD was not able to tell what version of SQL
server are they running.
DG

(provider: Named Pipes Provider,error: 40 - Could not open a connection to SQL Server)

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 am getting this error and using this connection string

Data Source=192.168.0.100;Network Library=DBMSSOCN;Initial Catalog=ENet;User ID=eonline;Password=eonline;

What can be solution for this.

you check if its firewall issue?|||see thing is that it is working gud but when my application connects to orcale and then when it come backs to connect sql it is giving error did it possible that oracle connection gives problem|||

Hi,

Since the error message contains "Could not open a connection to SQL Server", I think this error occurs when your app connects to a SQL Server. Based on the fact in your first post, have you checked if you have enabled remote connection on the server? Please following this KB article to achieve this.

http://support.microsoft.com/kb/914277/en-us

Currently, you're connecting to the database server using TCP/IP. You can also try to use Network Library=dbnmpntw to perform a named pipe connection.

|||I think I got a solution...

the error is in the connection string and in the configuration... if you'll use the IP instead of (loca), localhost, <machinename>\SQLEXPRESS, it will work. So use 127.0.0.1... the server will love it... and one more thing... at Protocols (SQL Server Configuration) at TCP/IP, set at IPAll - TCP Dymanic ports 1433 and one more... of course... set trusted connection to true... (you should allow remote connections too)..

So, the connection string is :

"Provider=SQLNCLI;Server=127.0.0.1;Database=database;Trusted_Connection=yes;"

Hope this helps someone..

P.S. : from my point of view.. I think this solution is a stupid one as long as local = localhost = 127.0.0.1... I guess for the SQLExpress... local = localhost != 127.0.0.1

(Problem) Named instance as SQLEXPRESS?

What if I give my named instance as SQLEXPRESS? I read that SQLEXPRESS

would be the name of the DEFAULT instance if no named instance is given.

In such a situation how can I find out if its a named or the default one?

SQLExpress is always a named instance.

jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Hi Ananda,

You might be a bit confused by the terms "default instance" and the fact that SQL Express is installed by default as a named instance.

Default Instance - This is the term we use to describe the copy of SQL Server that can be refered to by just the name of the computer in a connection string. There can only be one default instance of SQL Server on any computer. This is compared to a named instance, which is refered to by the <machine name>\<named instance name> in the connection string.

As Jens points out, SQL Express is installed by default as a named instance, and that named instance is SQLEXPRESS. If you specified SQLEXPRESS for the INSTANCENAME parameter in a command line install, or in the UI, you have installed a named instance. You can also install to a different named instance (up to 16 different instances for SQL Express) or you can install SQL Express as the default instance, but the default instance does not have a specific instance name.

Mike