An error has occurred while establishing a connection to the server

[Chazam]

Enviroment with Problem
SERVER 2003
SQL SERVER 2005
DEV C# .NET 2.0

I have a web application that works perfect on my dev machine. When I
publish it to my 2003 server it display this 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)

This happens to me when I try to access some aspx pages that resides
inside of folder call "po". How ever there are no problems on any root
aspx files of my web application. The "po" folder has no config file
just 2 more folders for images and 4 aspx pages on the root of this
"po" folder. Those pages send info to the database.

Hope some one help me on this
Thanks

 

[Nicholas Paldino [.NET/C# MVP]]

Chazam,

The exception message seems to tell it all. If you are connecting to
SQL Server 2005, by default, the named pipes provider is not enabled. You
have to enable the named pipes provider on the SQL Server 2005 machine in
order to allow connections from the machine hosting your web app.

 

[Chazam]

they ara enabled.
Like I said all may aspx pages works perfect except the ones resides
on the "po" folder
there is no problem with sql connection with pages out of this folder.

Chazam,

The exception message seems to tell it all. If you are connecting to
SQL Server 2005, by default, the named pipes provider is not enabled. You
have to enable the named pipes provider on the SQL Server 2005 machine in
order to allow connections from the machine hosting your web app.

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Enviroment with Problem
SERVER 2003
SQL SERVER 2005
DEV C# .NET 2.0

I have a web application that works perfect on my dev machine. When I
publish it to my 2003 server it display this 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)

This happens to me when I try to access some aspx pages that resides
inside of folder call "po". How ever there are no problems on any root
aspx files of my web application. The "po" folder has no config file
just 2 more folders for images and 4 aspx pages on the root of this
"po" folder. Those pages send info to the database.

Hope some one help me on this
Thanks- Hide quoted text -

- Show quoted text -

 

[Chazam]

Enviroment with Problem
SERVER 2003
SQL SERVER 2005 REMOTE CONNECTION ARE ENABLE
DEV C# .NET 2.0

I have a web application that works perfect on my dev machine. When I
publish it to my 2003 server it display this 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)


This happens to me when I try to access some aspx pages that resides
inside of folder call "po". How ever there are no problems on any
root
aspx files of my web application. The "po" folder has no config file
just 2 more folders for images and 4 aspx pages on the root of this
"po" folder. Those pages send info to the database.

 

[Nicholas Paldino [.NET/C# MVP]]

Chazam,

Yes, you said your pages work perfect, but are you actually doing any
data access on those pages? From your original post, it doesn't seem like
it does.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

they ara enabled.
Like I said all may aspx pages works perfect except the ones resides
on the "po" folder
there is no problem with sql connection with pages out of this folder.

Chazam,

The exception message seems to tell it all. If you are connecting to
SQL Server 2005, by default, the named pipes provider is not enabled.
You
have to enable the named pipes provider on the SQL Server 2005 machine in
order to allow connections from the machine hosting your web app.

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Enviroment with Problem
SERVER 2003
SQL SERVER 2005
DEV C# .NET 2.0

I have a web application that works perfect on my dev machine. When I
publish it to my 2003 server it display this 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)

This happens to me when I try to access some aspx pages that resides
inside of folder call "po". How ever there are no problems on any root
aspx files of my web application. The "po" folder has no config file
just 2 more folders for images and 4 aspx pages on the root of this
"po" folder. Those pages send info to the database.

Hope some one help me on this
Thanks- Hide quoted text -

- Show quoted text -

 

[Chazam]

Yup all d aspx pages have data acces. I mean all of them.

Chazam,

Yes, you said your pages work perfect, but are you actually doing any
data access on those pages? From your original post, it doesn't seem like
it does.

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

they ara enabled.
Like I said all may aspx pages works perfect except the ones resides
on the "po" folder
there is no problem with sql connection with pages out of this folder.

Chazam,
The exception message seems to tell it all. If you are connecting to
SQL Server 2005, by default, the named pipes provider is not enabled.
You
have to enable the named pipes provider on the SQL Server 2005 machine in
order to allow connections from the machine hosting your web app.
--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Enviroment with Problem
SERVER 2003
SQL SERVER 2005
DEV C# .NET 2.0
I have a web application that works perfect on my dev machine. When I
publish it to my 2003 server it display this 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)
This happens to me when I try to access some aspx pages that resides
inside of folder call "po". How ever there are no problems on any root
aspx files of my web application. The "po" folder has no config file
just 2 more folders for images and 4 aspx pages on the root of this
"po" folder. Those pages send info to the database.
Hope some one help me on this
Thanks- Hide quoted text -
- Show quoted text -- Hide quoted text -

- Show quoted text -

 

[roundcrisis]

Yup all d aspx pages have data acces. I mean all of them.

Chazam,

Yes, you said your pages work perfect, but are you actually doing any
data access on those pages? From your original post, it doesn't seem like
itdoes.

news:[email protected]...

they ara enabled.
Like I said allmayaspx pages works perfect except the ones resides
on the "po" folder
there is no problem withsqlconnectionwith pages out of this folder.
On Sep 18, 2:33 pm, "Nicholas Paldino [.NET/C# MVP]"
Chazam,
The exception message seems to tell it all. If you areconnectingto
SQLServer2005, bydefault, the named pipes provider isnotenabled.
You
have to enable the named pipes provider on theSQLServer2005machine in
order toallowconnectionsfrom the machine hosting your web app.
--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Enviroment with Problem
SERVER2003
SQLSERVER2005
DEV C# .NET 2.0
I have a web application that works perfect on my dev machine. When I
publish it to my 2003serverit display thiserror
Anerrorhasoccurredwhileestablishingaconnectionto theserver.
WhenconnectingtoSQLServer2005, thisfailuremaybecausedby the
factthatunderthedefaultsettingsSQLServerdoesnotallowremote
connections. (provider: Named Pipes Provider,error: 40 - Couldnot
open aconnectiontoSQLServer)
This happens to me when I try to access some aspx pages that resides
inside of folder call "po". How ever there are no problems on any root
aspx files of my web application. The "po" folderhasno config file
just 2 more folders for images and 4 aspx pages on the root of this
"po" folder. Those pages send info to the database.
Hope some one help me on this
Thanks- Hide quoted text -
- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

I have the same problem any luck?

 

[roundcrisis]

Yup all d aspx pages have data acces. I mean all of them.

Chazam,
Yes, you said your pages work perfect, but are you actually doing any
data access on those pages? From your original post, it doesn't seem like
itdoes.
--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

they ara enabled.
Like I said allmayaspx pages works perfect except the ones resides
on the "po" folder
there is no problem withsqlconnectionwith pages out of this folder.
On Sep 18, 2:33 pm, "Nicholas Paldino [.NET/C# MVP]"
Chazam,
The exception message seems to tell it all. If you areconnectingto
SQLServer2005, bydefault, the named pipes provider isnotenabled.
You
have to enable the named pipes provider on theSQLServer2005machine in
order toallowconnectionsfrom the machine hosting your web app.
--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Enviroment with Problem
SERVER2003
SQLSERVER2005
DEV C# .NET 2.0
I have a web application that works perfect on my dev machine. When I
publish it to my 2003serverit display thiserror
Anerrorhasoccurredwhileestablishingaconnectionto theserver.
WhenconnectingtoSQLServer2005, thisfailuremaybecausedby the
factthatunderthedefaultsettingsSQLServerdoesnotallowremote
connections. (provider: Named Pipes Provider,error: 40 - Couldnot
open aconnectiontoSQLServer)
This happens to me when I try to access some aspx pages that resides
inside of folder call "po". How ever there are no problems on any root
aspx files of my web application. The "po" folderhasno config file
just 2 more folders for images and 4 aspx pages on the root of this
"po" folder. Those pages send info to the database.
Hope some one help me on this
Thanks- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -- Hide quoted text -

- Show quoted text -

I have the same problem any luck?- Hide quoted text -

- Show quoted text -

in my case the connection string was wrong, because of the quotes i
had to use double backlash stupid error that took a long time,

 

[jeremycod]

Have you solved this problem?

Chasam,

Have you ever solved this problem? I got exactly the same problem

Zoran

 

[shijobaby]

Hi

If you wants to know how to enable remote connections

in sql server 2005 pls visit this

http://aspnetmembershipprovider.blogspot.com/2009/02/eanble-remote-connections-on-instance.html


Regards

 

[shijobaby]

Hi

i was facing the error when opening connection using sqlconnection

nw got solved


http://sqlservererror-info.blogspot.com/2009/07/error-has-occurred-while-establishing.html

http://aspnetmembershipprovider.blogspot.com/2009/02/error-has-occurred-while-establishing.html


See This

 

[shijobaby]

Hi

i was facing the error when opening connection using sqlconnection

nw got solved


http://sqlservererror-info.blogspot.com/2009/07/error-has-occurred-while-establishing.html

http://aspnetmembershipprovider.blogspot.com/2009/02/error-has-occurred-while-establishing.html


See This