Is using the named pipes protocol more/less secure and/or
slower than using tcpip to connect to SQL server?
"Colleen Rossman" <anonymous@.discussions.microsoft.com> wrote in message
news:136401c4aba9$c7ef54b0$a601280a@.phx.gbl...
> Is using the named pipes protocol more/less secure and/or
> slower than using tcpip to connect to SQL server?
Named Pipes is equally secure (ie, vulerable to ethernet sniffing).
In two special cases Named Pipes is faster: on the same machine, and over
local-area networks using the NetBUI protocol. In other cases TCP/IP is
faster, since in those cases Named Pipes would be running _over_ TCP/IP.
Remember that all the client netlibs date from before TCP/IP took over the
world. Back then you would choose the netlib which matched your LAN's
network protocol. Well today every network runs on IP, so everyone uses the
TCP/IP netlib.
David
Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts
Friday, March 30, 2012
named pipes under alias
I have a SQLSERVER INSTANCE A, to which I want to connect from a Client as TEST, using the SQL Server alias functionality under the client network utility program. The alias is working fine with the TCP\IP connection but it fails when I try to connect to the SQL Server using the named pipes. In my case I'm trying to connect to a named instance of SQL Server 2000 using the following pipe: \\servername\pipe\mssql$instancename\sql\query
Any help?I have just tried this. Pain in the neck, too. When you change the name of the alias, the client network utility is all helpful, and changes the actual path, and server name. So you have to get the right path, and save it of in notepad or something. Change the name of the alias, replace the name of the server with the name of the server you want, then recover the path from notepad. I tried it, and it did not work. Then I hit the Apply button. Now it works. Does that approximate what you went through?|||I can connect to any server using the alias name with the TCP/IP, but the same doesn't work with the Named Pipes.
Any help?I have just tried this. Pain in the neck, too. When you change the name of the alias, the client network utility is all helpful, and changes the actual path, and server name. So you have to get the right path, and save it of in notepad or something. Change the name of the alias, replace the name of the server with the name of the server you want, then recover the path from notepad. I tried it, and it did not work. Then I hit the Apply button. Now it works. Does that approximate what you went through?|||I can connect to any server using the alias name with the TCP/IP, but the same doesn't work with the Named Pipes.
Wednesday, March 28, 2012
Named Pipes Provider, error: 40 - Could not open a connection
Ok,
I've spent a bunch of hours trying to figure out how to connect to SQL
Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
I can run ASP.net code with no problem. I can access SQL Server from the
command line using osql with no problem.
But trying to access sql server 2005 from asp.net yields the following
message:
System.Data.SqlClient.SqlException: 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)
Can someone help me with this? I have both tcp/ip and named pipes enabled.
--
ThanksCan you post your connection string?
specifying
Network=DBMSSOCN
in your connection string will cause it to use tcp instead of named pipes,
which is less error prone.
See here for more details:
http://www.aspfaq.com/show.asp?id=2126
Also, check out the post regarding connections to sql express.
http://www.aspfaq.com/sql2005/show.asp?id=3
HTH
--
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> Ok,
> I've spent a bunch of hours trying to figure out how to connect to SQL
> Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> I can run ASP.net code with no problem. I can access SQL Server from the
> command line using osql with no problem.
> But trying to access sql server 2005 from asp.net yields the following
> message:
> System.Data.SqlClient.SqlException: 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)
> Can someone help me with this? I have both tcp/ip and named pipes enabled.
> --
> Thanks|||The connections string is:
Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
Catalog=sqlexpress;Integrated Security=SSPI");
The new error message I get is:
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.)
The detail is as follows:
System.Data.SqlClient.SqlException: 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: TCP Provider, error: 0 - No connection
could be made because the target machine actively refused it.)
It appears that the connection is blocked but I'm not sure where. I've
checked Windows Firewall and made sure that the appropriate ports are open...
--
Thanks
"Ryan Powers" wrote:
> Can you post your connection string?
> specifying
> Network=DBMSSOCN
> in your connection string will cause it to use tcp instead of named pipes,
> which is less error prone.
> See here for more details:
> http://www.aspfaq.com/show.asp?id=2126
> Also, check out the post regarding connections to sql express.
> http://www.aspfaq.com/sql2005/show.asp?id=3
> HTH
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > Ok,
> >
> > I've spent a bunch of hours trying to figure out how to connect to SQL
> > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > I can run ASP.net code with no problem. I can access SQL Server from the
> > command line using osql with no problem.
> >
> > But trying to access sql server 2005 from asp.net yields the following
> > message:
> >
> > System.Data.SqlClient.SqlException: 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)
> >
> > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> >
> > --
> > Thanks|||Check out this link.
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
This is a post that explains exactly how to enable remote connections for
express.
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> The connections string is:
> Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> Catalog=sqlexpress;Integrated Security=SSPI");
> The new error message I get is:
> (provider: TCP Provider, error: 0 - No connection could be made because the
> target machine actively refused it.)
> The detail is as follows:
> System.Data.SqlClient.SqlException: 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: TCP Provider, error: 0 - No connection
> could be made because the target machine actively refused it.)
> It appears that the connection is blocked but I'm not sure where. I've
> checked Windows Firewall and made sure that the appropriate ports are open...
> --
> Thanks
>
> "Ryan Powers" wrote:
> > Can you post your connection string?
> >
> > specifying
> > Network=DBMSSOCN
> > in your connection string will cause it to use tcp instead of named pipes,
> > which is less error prone.
> >
> > See here for more details:
> > http://www.aspfaq.com/show.asp?id=2126
> >
> > Also, check out the post regarding connections to sql express.
> > http://www.aspfaq.com/sql2005/show.asp?id=3
> >
> > HTH
> >
> > --
> > Ryan Powers
> > Clarity Consulting
> > http://www.claritycon.com
> >
> >
> > "Greg" wrote:
> >
> > > Ok,
> > >
> > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > command line using osql with no problem.
> > >
> > > But trying to access sql server 2005 from asp.net yields the following
> > > message:
> > >
> > > System.Data.SqlClient.SqlException: 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)
> > >
> > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > >
> > > --
> > > Thanks|||Excellent! I had to change from dynamic to static TCP port number. It works
great now.
Thanks for all your help
Greg
"Ryan Powers" wrote:
> Check out this link.
> http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
> This is a post that explains exactly how to enable remote connections for
> express.
>
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > The connections string is:
> > Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> > Catalog=sqlexpress;Integrated Security=SSPI");
> >
> > The new error message I get is:
> > (provider: TCP Provider, error: 0 - No connection could be made because the
> > target machine actively refused it.)
> >
> > The detail is as follows:
> > System.Data.SqlClient.SqlException: 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: TCP Provider, error: 0 - No connection
> > could be made because the target machine actively refused it.)
> >
> > It appears that the connection is blocked but I'm not sure where. I've
> > checked Windows Firewall and made sure that the appropriate ports are open...
> >
> > --
> > Thanks
> >
> >
> > "Ryan Powers" wrote:
> >
> > > Can you post your connection string?
> > >
> > > specifying
> > > Network=DBMSSOCN
> > > in your connection string will cause it to use tcp instead of named pipes,
> > > which is less error prone.
> > >
> > > See here for more details:
> > > http://www.aspfaq.com/show.asp?id=2126
> > >
> > > Also, check out the post regarding connections to sql express.
> > > http://www.aspfaq.com/sql2005/show.asp?id=3
> > >
> > > HTH
> > >
> > > --
> > > Ryan Powers
> > > Clarity Consulting
> > > http://www.claritycon.com
> > >
> > >
> > > "Greg" wrote:
> > >
> > > > Ok,
> > > >
> > > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > > command line using osql with no problem.
> > > >
> > > > But trying to access sql server 2005 from asp.net yields the following
> > > > message:
> > > >
> > > > System.Data.SqlClient.SqlException: 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)
> > > >
> > > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > > >
> > > > --
> > > > Thanks
I've spent a bunch of hours trying to figure out how to connect to SQL
Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
I can run ASP.net code with no problem. I can access SQL Server from the
command line using osql with no problem.
But trying to access sql server 2005 from asp.net yields the following
message:
System.Data.SqlClient.SqlException: 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)
Can someone help me with this? I have both tcp/ip and named pipes enabled.
--
ThanksCan you post your connection string?
specifying
Network=DBMSSOCN
in your connection string will cause it to use tcp instead of named pipes,
which is less error prone.
See here for more details:
http://www.aspfaq.com/show.asp?id=2126
Also, check out the post regarding connections to sql express.
http://www.aspfaq.com/sql2005/show.asp?id=3
HTH
--
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> Ok,
> I've spent a bunch of hours trying to figure out how to connect to SQL
> Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> I can run ASP.net code with no problem. I can access SQL Server from the
> command line using osql with no problem.
> But trying to access sql server 2005 from asp.net yields the following
> message:
> System.Data.SqlClient.SqlException: 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)
> Can someone help me with this? I have both tcp/ip and named pipes enabled.
> --
> Thanks|||The connections string is:
Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
Catalog=sqlexpress;Integrated Security=SSPI");
The new error message I get is:
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.)
The detail is as follows:
System.Data.SqlClient.SqlException: 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: TCP Provider, error: 0 - No connection
could be made because the target machine actively refused it.)
It appears that the connection is blocked but I'm not sure where. I've
checked Windows Firewall and made sure that the appropriate ports are open...
--
Thanks
"Ryan Powers" wrote:
> Can you post your connection string?
> specifying
> Network=DBMSSOCN
> in your connection string will cause it to use tcp instead of named pipes,
> which is less error prone.
> See here for more details:
> http://www.aspfaq.com/show.asp?id=2126
> Also, check out the post regarding connections to sql express.
> http://www.aspfaq.com/sql2005/show.asp?id=3
> HTH
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > Ok,
> >
> > I've spent a bunch of hours trying to figure out how to connect to SQL
> > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > I can run ASP.net code with no problem. I can access SQL Server from the
> > command line using osql with no problem.
> >
> > But trying to access sql server 2005 from asp.net yields the following
> > message:
> >
> > System.Data.SqlClient.SqlException: 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)
> >
> > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> >
> > --
> > Thanks|||Check out this link.
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
This is a post that explains exactly how to enable remote connections for
express.
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> The connections string is:
> Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> Catalog=sqlexpress;Integrated Security=SSPI");
> The new error message I get is:
> (provider: TCP Provider, error: 0 - No connection could be made because the
> target machine actively refused it.)
> The detail is as follows:
> System.Data.SqlClient.SqlException: 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: TCP Provider, error: 0 - No connection
> could be made because the target machine actively refused it.)
> It appears that the connection is blocked but I'm not sure where. I've
> checked Windows Firewall and made sure that the appropriate ports are open...
> --
> Thanks
>
> "Ryan Powers" wrote:
> > Can you post your connection string?
> >
> > specifying
> > Network=DBMSSOCN
> > in your connection string will cause it to use tcp instead of named pipes,
> > which is less error prone.
> >
> > See here for more details:
> > http://www.aspfaq.com/show.asp?id=2126
> >
> > Also, check out the post regarding connections to sql express.
> > http://www.aspfaq.com/sql2005/show.asp?id=3
> >
> > HTH
> >
> > --
> > Ryan Powers
> > Clarity Consulting
> > http://www.claritycon.com
> >
> >
> > "Greg" wrote:
> >
> > > Ok,
> > >
> > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > command line using osql with no problem.
> > >
> > > But trying to access sql server 2005 from asp.net yields the following
> > > message:
> > >
> > > System.Data.SqlClient.SqlException: 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)
> > >
> > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > >
> > > --
> > > Thanks|||Excellent! I had to change from dynamic to static TCP port number. It works
great now.
Thanks for all your help
Greg
"Ryan Powers" wrote:
> Check out this link.
> http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
> This is a post that explains exactly how to enable remote connections for
> express.
>
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > The connections string is:
> > Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> > Catalog=sqlexpress;Integrated Security=SSPI");
> >
> > The new error message I get is:
> > (provider: TCP Provider, error: 0 - No connection could be made because the
> > target machine actively refused it.)
> >
> > The detail is as follows:
> > System.Data.SqlClient.SqlException: 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: TCP Provider, error: 0 - No connection
> > could be made because the target machine actively refused it.)
> >
> > It appears that the connection is blocked but I'm not sure where. I've
> > checked Windows Firewall and made sure that the appropriate ports are open...
> >
> > --
> > Thanks
> >
> >
> > "Ryan Powers" wrote:
> >
> > > Can you post your connection string?
> > >
> > > specifying
> > > Network=DBMSSOCN
> > > in your connection string will cause it to use tcp instead of named pipes,
> > > which is less error prone.
> > >
> > > See here for more details:
> > > http://www.aspfaq.com/show.asp?id=2126
> > >
> > > Also, check out the post regarding connections to sql express.
> > > http://www.aspfaq.com/sql2005/show.asp?id=3
> > >
> > > HTH
> > >
> > > --
> > > Ryan Powers
> > > Clarity Consulting
> > > http://www.claritycon.com
> > >
> > >
> > > "Greg" wrote:
> > >
> > > > Ok,
> > > >
> > > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > > command line using osql with no problem.
> > > >
> > > > But trying to access sql server 2005 from asp.net yields the following
> > > > message:
> > > >
> > > > System.Data.SqlClient.SqlException: 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)
> > > >
> > > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > > >
> > > > --
> > > > Thanks
Named Pipes Provider, error: 40 - Could not connect; Error 2
I have installed MSSQL 2005 successfuly, checked the services their are running I can connect to the
server with Intergrations Services ok. I get the following when I try to connect to the Database Engine
(provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
What file is SQL looking for (net helpmsg 2)?
Thanks for the help
Did you enable remote conenctions ? Check my website for the screencast which explains how to enable the Remote connections on your instance.Jens K. Suessmeyer
http://www.sqlserver2005.de
|||Would this be true for a standalone PC? I don't have SQL Server installed on a remote server.|||
For a standalone PC, you want to disable remote connections for TCP/IP and Named Pipes but you probably want to enable them locally (especially considering that you are trying to use named pipes here). So you should start SQL Server Configuration Manager, then go to "Protocols" then enable both TCP/IP and Named Pipes. To make sure that remote computers cannot connect to your machine -- go to SQL Server Surface Area Configuration -> Surface Area Configuration for Services and Connections ->Remote Connections and turn off remote connections.
That should do it,
John
Named Pipes Provider, error: 40 - Could not connect; Error 2
I have installed MSSQL 2005 successfuly, checked the services their are running I can connect to the
server with Intergrations Services ok. I get the following when I try to connect to the Database Engine
(provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
What file is SQL looking for (net helpmsg 2)?
Thanks for the help
Did you enable remote conenctions ? Check my website for the screencast which explains how to enable the Remote connections on your instance.Jens K. Suessmeyer
http://www.sqlserver2005.de
|||Would this be true for a standalone PC? I don't have SQL Server installed on a remote server.|||
For a standalone PC, you want to disable remote connections for TCP/IP and Named Pipes but you probably want to enable them locally (especially considering that you are trying to use named pipes here). So you should start SQL Server Configuration Manager, then go to "Protocols" then enable both TCP/IP and Named Pipes. To make sure that remote computers cannot connect to your machine -- go to SQL Server Surface Area Configuration -> Surface Area Configuration for Services and Connections ->Remote Connections and turn off remote connections.
That should do it,
John
named pipes
The cluster consists of two nodes and of two instances. One default sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
Have you run cliconfg.exe on both nodes, not just the "primary"?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
The cluster consists of two nodes and of two instances. One default sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
|||I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>=20
>=20
>=20
> Thanks in advance.
> Andrew
|||This sounds strange. Have you tried removing the aliases from the client
machines?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau писал(а):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
> Thanks in advance.
> Andrew
|||If i remove - i just can't connect..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
|||This sounds like either a DNS issue or that SQL Server is not listening on
TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
Server errorlog to see what protocols SQL Server will "hear". Also, ensure
that your clients are using TCP/IP. Check out their Client Network Utility
to confirm.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
If i remove - i just can't connect..
Andrew
Tom Moreau писал(а):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau писал(а):
|||with tcp/ip everything is ok. I've a problem with named pipes. Our
application isn't tcp/ip aware, just named pipes - thats all.
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> This sounds like either a DNS issue or that SQL Server is not listening on
> TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
> Server errorlog to see what protocols SQL Server will "hear". Also, ensu=
re
> that your clients are using TCP/IP. Check out their Client Network Utili=
ty[vbcol=seagreen]
> to confirm.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
> If i remove - i just can't connect..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
nt[vbcol=seagreen]
ql[vbcol=seagreen]
s?[vbcol=seagreen]
|||ok, for example
Active-Active cluster. One instance server1, another one -
server2\instance
Since my application isnt't cluster aware i create an alias to connect
via named pipes.
- server alias: server2
- server name: server2\instance
- pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
when server2 fails over to server1 i can't use my application. At this
moment I can ping server2 successfully.
If i change on the client the alias server2:
- server alias: server2 (it's the same)
- server name: server1
- pipe name: \\server1\pipe\\sql\query
I can connect and can't use my application
|||kreit wrote:
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
Maybe some of the registry is not replicated. In the cluster registry
there should be about 7 registry entries for each sql server resource
which are used to replicate some of the sql registry keys. Check if they
exist. Also check the contents of software\microsoft\microsoft sql
server\instance\mssqlserver\supersocketnetlib\np\p ipename on the problem
node when sql is running there.
The service account of the default instance should be able to read the
registry key's of the named instance and vice versa. Sqlservers log
mentions its listening on named pipes?
What I think is kind of strange is that you are able to use the client
network tools aliases but not tcp\ip. Your program should not even know
about named pipes or tcp/ip. It just needs to talk to the sqldriver.
Maybe its time to instal ethereal (http://www.ethereal.com/) on one of
the clients.
Hans
|||kreit wrote:
> ok, for example
> Active-Active cluster. One instance server1, another one -
> server2\instance
> Since my application isnt't cluster aware i create an alias to connect
> via named pipes.
> - server alias: server2
> - server name: server2\instance
> - pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
>
> when server2 fails over to server1 i can't use my application. At this
> moment I can ping server2 successfully.
> If i change on the client the alias server2:
> - server alias: server2 (it's the same)
> - server name: server1
> - pipe name: \\server1\pipe\\sql\query
> I can connect and can't use my application
>
Just to make very sure, you do know the difference between the virtual
server name and the node name?
'when server2 fails over to server1 i can't use my application'
should be:
'when virtual server2 fails over to node1 i can't use my application'
Clients should connect to the virtual server name and not to the not to
the name of the physical server.
Hans
sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
Have you run cliconfg.exe on both nodes, not just the "primary"?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
The cluster consists of two nodes and of two instances. One default sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
|||I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>=20
>=20
>=20
> Thanks in advance.
> Andrew
|||This sounds strange. Have you tried removing the aliases from the client
machines?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
I run cliconfg.exe on the clients side. The problem is that our
end-user applications aren't ms sql instances aware of and i need to
provide an alias.
i can change the alias on the user machines via some kind of gpo etc..
Andrew
Tom Moreau писал(а):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.com...
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
> Thanks in advance.
> Andrew
|||If i remove - i just can't connect..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
|||This sounds like either a DNS issue or that SQL Server is not listening on
TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
Server errorlog to see what protocols SQL Server will "hear". Also, ensure
that your clients are using TCP/IP. Check out their Client Network Utility
to confirm.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
If i remove - i just can't connect..
Andrew
Tom Moreau писал(а):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.com...
> I run cliconfg.exe on the clients side. The problem is that our
> end-user applications aren't ms sql instances aware of and i need to
> provide an alias.
> i can change the alias on the user machines via some kind of gpo etc..
> Andrew
> Tom Moreau писал(а):
|||with tcp/ip everything is ok. I've a problem with named pipes. Our
application isn't tcp/ip aware, just named pipes - thats all.
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> This sounds like either a DNS issue or that SQL Server is not listening on
> TCP/IP. Check out the Server Network Utility on your cluster - or the SQL
> Server errorlog to see what protocols SQL Server will "hear". Also, ensu=
re
> that your clients are using TCP/IP. Check out their Client Network Utili=
ty[vbcol=seagreen]
> to confirm.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
> If i remove - i just can't connect..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
nt[vbcol=seagreen]
ql[vbcol=seagreen]
s?[vbcol=seagreen]
|||ok, for example
Active-Active cluster. One instance server1, another one -
server2\instance
Since my application isnt't cluster aware i create an alias to connect
via named pipes.
- server alias: server2
- server name: server2\instance
- pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
when server2 fails over to server1 i can't use my application. At this
moment I can ping server2 successfully.
If i change on the client the alias server2:
- server alias: server2 (it's the same)
- server name: server1
- pipe name: \\server1\pipe\\sql\query
I can connect and can't use my application
|||kreit wrote:
> The cluster consists of two nodes and of two instances. One default sql
> instance and one another named instanse.
>
> To connect to the named instance all the clients have alias(done by
> cliconfg.exe), but when the instance fails over to another node no one
> can't connect to this named instance anymore. If i edit the alias to
> use the default instance pipe name, this helps!
>
> It seems named pipes don't fail over to another node.. Any suggestions?
>
Maybe some of the registry is not replicated. In the cluster registry
there should be about 7 registry entries for each sql server resource
which are used to replicate some of the sql registry keys. Check if they
exist. Also check the contents of software\microsoft\microsoft sql
server\instance\mssqlserver\supersocketnetlib\np\p ipename on the problem
node when sql is running there.
The service account of the default instance should be able to read the
registry key's of the named instance and vice versa. Sqlservers log
mentions its listening on named pipes?
What I think is kind of strange is that you are able to use the client
network tools aliases but not tcp\ip. Your program should not even know
about named pipes or tcp/ip. It just needs to talk to the sqldriver.
Maybe its time to instal ethereal (http://www.ethereal.com/) on one of
the clients.
Hans
|||kreit wrote:
> ok, for example
> Active-Active cluster. One instance server1, another one -
> server2\instance
> Since my application isnt't cluster aware i create an alias to connect
> via named pipes.
> - server alias: server2
> - server name: server2\instance
> - pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query
>
> when server2 fails over to server1 i can't use my application. At this
> moment I can ping server2 successfully.
> If i change on the client the alias server2:
> - server alias: server2 (it's the same)
> - server name: server1
> - pipe name: \\server1\pipe\\sql\query
> I can connect and can't use my application
>
Just to make very sure, you do know the difference between the virtual
server name and the node name?
'when server2 fails over to server1 i can't use my application'
should be:
'when virtual server2 fails over to node1 i can't use my application'
Clients should connect to the virtual server name and not to the not to
the name of the physical server.
Hans
sql
Named Pipers Provider, error 40, ok from local, error to remote - help
Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald|||Do you have to connect with named pipes? If not, change the connection string
to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
connectivity components are properly installed on the web server and you can
ping the database server from the web server, I'd try a few things.
1. Find out the IP address and the TCP port that the SQL instance listens on.
2. Change the connection string to the IP address followed by a comma and
then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
you may have a problem with accessing the port. (if it's the default instance
using the default port, you don't need to test with the port number specified
explicitly).
3. Change the IP to the server name in the Server property of the connection
string, and try again. If this doesn't work, you may have a problem with
resolving the server to the IP address. Try the fully qualified domain name
instead.
If you can connect with TCP/IP, but not with names pipes, you may have a
problem with the ports used by the named pipes being blocked.
Linchi
"Ranginald" wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
>|||How would I find out the TCP port that the SQL instance listens on?
Thanks
Linchi Shea wrote:
> Do you have to connect with named pipes? If not, change the connection string
> to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
> connectivity components are properly installed on the web server and you can
> ping the database server from the web server, I'd try a few things.
> 1. Find out the IP address and the TCP port that the SQL instance listens on.
> 2. Change the connection string to the IP address followed by a comma and
> then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
> you may have a problem with accessing the port. (if it's the default instance
> using the default port, you don't need to test with the port number specified
> explicitly).
> 3. Change the IP to the server name in the Server property of the connection
> string, and try again. If this doesn't work, you may have a problem with
> resolving the server to the IP address. Try the fully qualified domain name
> instead.
> If you can connect with TCP/IP, but not with names pipes, you may have a
> problem with the ports used by the named pipes being blocked.
> Linchi
> "Ranginald" wrote:
> > Hi.
> >
> > I am new to sql server so please bear with me.
> > Here is the problem.
> >
> > I am using VWD express to connect to a sql server 2005 db on my local
> > machine. The site and the sql server are local and everything is fine.
> > No problems.
> >
> > I have a sql server hosting plan to host the db. (my local is SQL
> > Server 2005 and the hosted is Sql Server 2000).
> >
> > I use the LOCAL VWD website to access the HOSTED sql server and it
> > connects with no problem. I changed data in the remote version of the
> > db as a double-check that I am accessing the remote db and not the
> > local db.
> >
> > When I go ahead and upload the web site to my web host, different from
> > the sql host (long story), I get this error (provider: Named Pipes
> > Provider, error: 40 - Could not open a connection to SQL Server).
> >
> > Any ideas why this error is happening. My web host verifies that my
> > connection string is fine, and that if I can connect with my local
> > machine then there should be no problem and the problems is on the
> > hosting end.
> >
> > Thanks in advance,
> > Ranginald
> >
> >sql
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald|||Do you have to connect with named pipes? If not, change the connection string
to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
connectivity components are properly installed on the web server and you can
ping the database server from the web server, I'd try a few things.
1. Find out the IP address and the TCP port that the SQL instance listens on.
2. Change the connection string to the IP address followed by a comma and
then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
you may have a problem with accessing the port. (if it's the default instance
using the default port, you don't need to test with the port number specified
explicitly).
3. Change the IP to the server name in the Server property of the connection
string, and try again. If this doesn't work, you may have a problem with
resolving the server to the IP address. Try the fully qualified domain name
instead.
If you can connect with TCP/IP, but not with names pipes, you may have a
problem with the ports used by the named pipes being blocked.
Linchi
"Ranginald" wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
>|||How would I find out the TCP port that the SQL instance listens on?
Thanks
Linchi Shea wrote:
> Do you have to connect with named pipes? If not, change the connection string
> to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
> connectivity components are properly installed on the web server and you can
> ping the database server from the web server, I'd try a few things.
> 1. Find out the IP address and the TCP port that the SQL instance listens on.
> 2. Change the connection string to the IP address followed by a comma and
> then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
> you may have a problem with accessing the port. (if it's the default instance
> using the default port, you don't need to test with the port number specified
> explicitly).
> 3. Change the IP to the server name in the Server property of the connection
> string, and try again. If this doesn't work, you may have a problem with
> resolving the server to the IP address. Try the fully qualified domain name
> instead.
> If you can connect with TCP/IP, but not with names pipes, you may have a
> problem with the ports used by the named pipes being blocked.
> Linchi
> "Ranginald" wrote:
> > Hi.
> >
> > I am new to sql server so please bear with me.
> > Here is the problem.
> >
> > I am using VWD express to connect to a sql server 2005 db on my local
> > machine. The site and the sql server are local and everything is fine.
> > No problems.
> >
> > I have a sql server hosting plan to host the db. (my local is SQL
> > Server 2005 and the hosted is Sql Server 2000).
> >
> > I use the LOCAL VWD website to access the HOSTED sql server and it
> > connects with no problem. I changed data in the remote version of the
> > db as a double-check that I am accessing the remote db and not the
> > local db.
> >
> > When I go ahead and upload the web site to my web host, different from
> > the sql host (long story), I get this error (provider: Named Pipes
> > Provider, error: 40 - Could not open a connection to SQL Server).
> >
> > Any ideas why this error is happening. My web host verifies that my
> > connection string is fine, and that if I can connect with my local
> > machine then there should be no problem and the problems is on the
> > hosting end.
> >
> > Thanks in advance,
> > Ranginald
> >
> >sql
Named Pipers Provider, error 40, ok from local, error to remote - help
Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
Monday, March 26, 2012
Named pipe error 53
I get the following error when I try to connect from an XP SP2 client to SQL
MSDE:
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) (Microsoft SQL Server, Error: 53)
Before last week, al worked fine, but suddenly I get this message.
What goes wrong?Is the service on another machine ? Can you reach the computer via ping ?
Did you try disabling the firewall on the Windows XP machine to see if it is
dedicted to the settings of the firewall ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Johan" <Johan@.discussions.microsoft.com> wrote in message
news:68D2C2C3-B0B1-4756-BBBD-B6A6D2577EDA@.microsoft.com...
>I get the following error when I try to connect from an XP SP2 client to
>SQL
> MSDE:
> 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) (Microsoft SQL Server, Error: 53)
> Before last week, al worked fine, but suddenly I get this message.
> What goes wrong?sql
MSDE:
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) (Microsoft SQL Server, Error: 53)
Before last week, al worked fine, but suddenly I get this message.
What goes wrong?Is the service on another machine ? Can you reach the computer via ping ?
Did you try disabling the firewall on the Windows XP machine to see if it is
dedicted to the settings of the firewall ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Johan" <Johan@.discussions.microsoft.com> wrote in message
news:68D2C2C3-B0B1-4756-BBBD-B6A6D2577EDA@.microsoft.com...
>I get the following error when I try to connect from an XP SP2 client to
>SQL
> MSDE:
> 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) (Microsoft SQL Server, Error: 53)
> Before last week, al worked fine, but suddenly I get this message.
> What goes wrong?sql
Named Instances Problem (I Think)
I'm struggling a little with this. I hope someone can help.
Ho do i install SQL Server 2005 Express so i can connect to it with "localhost", not "<MACHINE_NAME>/SQLEXPRESS". I cant seem to find any obvious setting in setup.
Could anyone shed any light on this?
Regards,
Anthony
I think you want to connect only to default instance in that case just specify the instance name as default while installing sql express refer, http://msdn2.microsoft.com/en-us/library/ms143722.aspx|||
You can use an alias configured on the clients to connect to the name only. See the BOL for more information about configuring aliases. You will have to use the SQL Server configuration manager.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Friday, March 23, 2012
Named instance connection problem
Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
Named instance connection problem
Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
Named instance connection problem
Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
--
David Gugick
Quest Software
www.quest.comsql
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
--
David Gugick
Quest Software
www.quest.comsql
Named instance connection problem
Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
Named instance connection problem
Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
Named instance connection problem
Have an MSDE named instance which works just fine. Just installed
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
another instance of the same and can only connect to it using OSQL
locally, nothing across the network. I made sure to use all the
gotcha flags during install to enable network access, etc:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
c:\temp\msdeinstlog.txt
After the install and reboot, also verified that network access is
allowed using SVRNETCN, where both named pipes and TCP connections are
enabled.
Tried connecting using "sa" and trusted NT auth and both work locally,
but across the network it's always:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
No firewalls in the way from client to server. As a matter of fact,
when I telnet to the TCP port shown in SVRNETCN, the connection is
established, so the port is obviously open.
I'm racking my brain on this one... What gives?
Thanks guys,
-Peter.
Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
> I'm racking my brain on this one... What gives?
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/
David Gugick
Quest Software
www.quest.com
Named instance and JDBC driver
I have named SQL Server 200 instance installed.
I am trying to connect to connect this named instance using
java application which using JDBC driver ?
anybody knows how can I connect named instance using JDBC driver ?
thank you for timely help
jagdishYou have to use the port number for the named sql server instance:
e.g.
jdbc:microsoft:sqlserver://servername:portnumber;user=XXX;password=YYY
I am trying to connect to connect this named instance using
java application which using JDBC driver ?
anybody knows how can I connect named instance using JDBC driver ?
thank you for timely help
jagdishYou have to use the port number for the named sql server instance:
e.g.
jdbc:microsoft:sqlserver://servername:portnumber;user=XXX;password=YYY
Named Instance
I couldn't connect to named instance in my client machine... I recieved the
error messange.. SQL Server Doesn't exist or Access denied. Can any one
guide me...
Thanks
See if this helps?
http://support.microsoft.com/default...265808&sd=tech
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Roy" <roy@.hotmail.com> wrote in message
news:eVq00F$hFHA.500@.TK2MSFTNGP09.phx.gbl...
>I couldn't connect to named instance in my client machine... I recieved the
> error messange.. SQL Server Doesn't exist or Access denied. Can any one
> guide me...
> Thanks
>
>
sql
error messange.. SQL Server Doesn't exist or Access denied. Can any one
guide me...
Thanks
See if this helps?
http://support.microsoft.com/default...265808&sd=tech
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Roy" <roy@.hotmail.com> wrote in message
news:eVq00F$hFHA.500@.TK2MSFTNGP09.phx.gbl...
>I couldn't connect to named instance in my client machine... I recieved the
> error messange.. SQL Server Doesn't exist or Access denied. Can any one
> guide me...
> Thanks
>
>
sql
name resolution (WINS/DNS)
How does the name of a datasource get resolved?
I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links
. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location.
For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged.
However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advanceRE:
How does the name of a datasource get resolved? I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location. For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged. However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advance
S1: Aspects of the situation strike me as potentially 'radioactive'.
S2: I strongly suggest you work closely with your friendly network engineer e.g. (look out for looping and things like that), and carefully test whatever schemes you test / work out (working toghther). What will work depends on how the entire environment is configured. Be sure to take into full consideration any and all things that might be involved or interact with potential solutions at any level, e.g.(like VPNs, dial ups, and other connections between sites).
S3: Alternative general approaches that may be workable (or not, and in any event potentially reckless, if you just 'dive in'):
i) Add site logon scripts that strip any locally cached and/or stored references to DBServer from when the (roaming laptop) was at other sites e.g.(including dsns, added routes, Hosts, lmhosts, arp, etc. data and other entries that may be applicable in your environment).
ii) Bind all the ips of the various DBServers to each and every DBServer.sql
I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links
. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location.
For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged.
However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advanceRE:
How does the name of a datasource get resolved? I have a situation where users with notebooks work in several different sites- and need to connect to the database server in the current location, rather than connection to the DB in their 'home' location which is over slow WAN links. Rather than setting up multiple static database connections (difficult to manage & difficult for users) I hope to use WINS/internal DNS to resolve a hostname to the correct IP address/database server for each location. For example, the database connection would be something like:
defaultdsn=DRIVER=SQL Server;UID=***;PWD=***;DATABASE=DB1;SERVER=DBSERVE R\DB1
For location 1:
192.168.150.6 DBSERVER
For location 2:
192.168.161.8 DBSERVER
For location 3:
192.168.162.8 DBSERVER
If I use WINS at each location as above, the hostname gets resolved & can be pinged. However- for the database connection, I cannot make a connection using this approach- I've tried different combinations of named pipes etc etc.
thanks in advance
S1: Aspects of the situation strike me as potentially 'radioactive'.
S2: I strongly suggest you work closely with your friendly network engineer e.g. (look out for looping and things like that), and carefully test whatever schemes you test / work out (working toghther). What will work depends on how the entire environment is configured. Be sure to take into full consideration any and all things that might be involved or interact with potential solutions at any level, e.g.(like VPNs, dial ups, and other connections between sites).
S3: Alternative general approaches that may be workable (or not, and in any event potentially reckless, if you just 'dive in'):
i) Add site logon scripts that strip any locally cached and/or stored references to DBServer from when the (roaming laptop) was at other sites e.g.(including dsns, added routes, Hosts, lmhosts, arp, etc. data and other entries that may be applicable in your environment).
ii) Bind all the ips of the various DBServers to each and every DBServer.sql
name pipe VS tcpip
I found that I can only use name pipe to connect to the sql server.
When I use tcpip, it fails to connect.
I am sure I have enabled the TCP/IP protocol in SQL server
What causes it?
sql is using port no.1433 and I have try using dynamically determine port
and force it to 1433 in ODBC setting.
thank you very much
"!" <!@.!.!> wrote in message news:%236FqHb0qEHA.3416@.TK2MSFTNGP15.phx.gbl...
> I found that I can only use name pipe to connect to the sql server.
> When I use tcpip, it fails to connect.
> I am sure I have enabled the TCP/IP protocol in SQL server
> What causes it?
> sql is using port no.1433 and I have try using dynamically determine port
> and force it to 1433 in ODBC setting.
There are a lot of reasons that this can fail, application type being one of
them. Reference the following as a troubleshooting guide:
http://support.microsoft.com/default...b;en-us;827422
Steve
When I use tcpip, it fails to connect.
I am sure I have enabled the TCP/IP protocol in SQL server
What causes it?
sql is using port no.1433 and I have try using dynamically determine port
and force it to 1433 in ODBC setting.
thank you very much
"!" <!@.!.!> wrote in message news:%236FqHb0qEHA.3416@.TK2MSFTNGP15.phx.gbl...
> I found that I can only use name pipe to connect to the sql server.
> When I use tcpip, it fails to connect.
> I am sure I have enabled the TCP/IP protocol in SQL server
> What causes it?
> sql is using port no.1433 and I have try using dynamically determine port
> and force it to 1433 in ODBC setting.
There are a lot of reasons that this can fail, application type being one of
them. Reference the following as a troubleshooting guide:
http://support.microsoft.com/default...b;en-us;827422
Steve
Subscribe to:
Posts (Atom)