By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,857 Members | 1,835 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,857 IT Pros & Developers. It's quick & easy.

ASP.NET 2.0 and connection to remote SQL 2000 server

P: n/a
Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no any
2005 server on remote server!

This is my connection string:
Server=servername;Database=SOX;User ID=userxxx;Password=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed on
production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only ASP.NET
2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?
Aug 5 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Try changing the connection string to reflect the actual address to server,
that may include changing that information in the web.config file...

This is my connection string:

Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******;

"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:uT**************@TK2MSFTNGP04.phx.gbl...
Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database
and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no any
2005 server on remote server!

This is my connection string:
Server=servername;Database=SOX;User ID=userxxx;Password=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed on
production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only ASP.NET
2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?


Aug 5 '06 #2

P: n/a
Do you mean IP address? I tried, it didn't help :(

"Henry" <at**************@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******;

"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:uT**************@TK2MSFTNGP04.phx.gbl...
>Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database
and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no any
2005 server on remote server!

This is my connection string:
Server=servername;Database=SOX;User ID=userxxx;Password=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only ASP.NET
2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?



Aug 5 '06 #3

P: n/a
Mitya i think you might need to take some additional steps
See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm
Hope that helps
Patrick
"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:ex**************@TK2MSFTNGP03.phx.gbl...
Do you mean IP address? I tried, it didn't help :(

"Henry" <at**************@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
>Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******;

"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:uT**************@TK2MSFTNGP04.phx.gbl...
>>Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database
and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed on
another server.
I received the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no
any 2005 server on remote server!

This is my connection string:
Server=servername;Database=SOX;User ID=userxxx;Password=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only
ASP.NET 2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?




Aug 6 '06 #4

P: n/a
Thank you, but I use Sql Server 2000.

"Patrick.O.Ige" <na********@hotmail.comwrote in message
news:Ou**************@TK2MSFTNGP04.phx.gbl...
Mitya i think you might need to take some additional steps
See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm
Hope that helps
Patrick
"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:ex**************@TK2MSFTNGP03.phx.gbl...
>Do you mean IP address? I tried, it didn't help :(

"Henry" <at**************@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
>>Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******;

"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:uT**************@TK2MSFTNGP04.phx.gbl...
Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000
database and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed
on another server.
I received the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no
any 2005 server on remote server!

This is my connection string:
Server=servername;Database=SOX;User ID=userxxx;Password=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only
ASP.NET 2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?




Aug 6 '06 #5

P: n/a
You have to make sure that the remote server is not "Hidden" which would
prevent a remote connection; also check that BOTH Sql Server and Windows
Authentication are enabled.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Mitya Mitriev" wrote:
Thank you, but I use Sql Server 2000.

"Patrick.O.Ige" <na********@hotmail.comwrote in message
news:Ou**************@TK2MSFTNGP04.phx.gbl...
Mitya i think you might need to take some additional steps
See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm
Hope that helps
Patrick
"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:ex**************@TK2MSFTNGP03.phx.gbl...
Do you mean IP address? I tried, it didn't help :(

"Henry" <at**************@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
Try changing the connection string to reflect the actual address to
server, that may include changing that information in the web.config
file...

This is my connection string:

Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******;

"Mitya Mitriev" <aa*@stopspam.orgwrote in message
news:uT**************@TK2MSFTNGP04.phx.gbl...
Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000
database and
it works perfectly when website and Sql server were on local machine.

Then I installed application on production server. Database is placed
on another server.
I received the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)

Why it thinks I am trying to connect to SQL Server 2005 ? There is no
any 2005 server on remote server!

This is my connection string:
Server=servername;Database=SOX;User ID=userxxx;Password=******;

Query Analyzer and Enterprise Manager connect perfectly (when installed
on production server) to database server! Then I created small console
appplication which uses the same data layer as web application (and
connection string ) - it connected to remote database too! Only
ASP.NET 2.0 application couldn't connect to remote Sql server 2000.

Can anyone help?



Aug 6 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.