ASP .net 1.2 connect to SQL

[patrick_keton]

I am trying to connect to a dabase located on server 2 from my asp.net
1.2 web pages located on server 1

Am using following connection string:

"Integrated Security=SSPI;Persist Security Info=False;User
ID=myuid;Password=mypass;Initial Catalog=mydb;Data Source=myserver"

Error returned by Server 2 is

Message: 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)
Line Number: 0
Source: .Net SqlClient Data Provider
Procedure:

Is there something wrong with my code.
Please advice

[Juan T. Llibre]

re:
!under the default settings SQL Server does not allow remote connections

Please review this KB :

http://support.microsoft.com/default...b;EN-US;914277

Also, for future inquiries, there's no "asp.net 1.2".
There's asp.net 1.1 and asp.net 2.0...but no asp.net 1.2.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
<pa***********@yahoo.comwrote in message news:11********************@z28g2000prd.googlegrou ps.com...

>I am trying to connect to a dabase located on server 2 from my asp.net
1.2 web pages located on server 1

Am using following connection string:

"Integrated Security=SSPI;Persist Security Info=False;User
ID=myuid;Password=mypass;Initial Catalog=mydb;Data Source=myserver"

Error returned by Server 2 is

Message: 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)
Line Number: 0
Source: .Net SqlClient Data Provider
Procedure:

Is there something wrong with my code.
Please advice

[Cowboy \(Gregory A. Beamer\)]

Simple:

1. Make sure you have a protocol you can talk to. By default, some versions
of SQL Server use in-memory only. Add a protocol like TCP using the SQL
Configuration tool.
2. Turn on the SQL Browser service in the services administration tool and
make sure it is set to start automatically when you reboot after patches.

After that, you should have no issues. Juan has also posted a link to a KB
article that has more detail.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************
<pa***********@yahoo.comwrote in message
news:11********************@z28g2000prd.googlegrou ps.com...

>I am trying to connect to a dabase located on server 2 from my asp.net
1.2 web pages located on server 1

Am using following connection string:

"Integrated Security=SSPI;Persist Security Info=False;User
ID=myuid;Password=mypass;Initial Catalog=mydb;Data Source=myserver"

Error returned by Server 2 is

Message: 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)
Line Number: 0
Source: .Net SqlClient Data Provider
Procedure:

Is there something wrong with my code.
Please advice

[patrick_keton]

Thanks a lot