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

Error "SQL Server does not allow remote connections"

P: n/a
I just deployed my new ASP.NET (3.5 FW) site to the hosting company I'm
using, webhost4life.

NOTE: I HAVE deployed other SQL Server sites to the same account with no
issues.

Now I'm getting this error. Any idea why?

Server Error in '/myuser4/MyWebApp' Application.
--------------------------------------------------------------------------------

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: 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)

Source Error:
Line 4:
Line 5: Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
Line 6: If User.IsInRole("LexAdmin") Or
User.IsInRole("LexOperator") Or User.IsInRole("LexUser") Then
Line 7: Response.Redirect("admin/ManagePackages.aspx")
Line 8: ElseIf User.IsInRole("CustomerAdmin") Or
User.IsInRole("CustomerClient") Or User.IsInRole("CustomerUser") Then
Source File: d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb
Line: 6

Stack Trace:
[SqlException (0x80131904): 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)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection) +800131
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj) +186
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject) +737554
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject) +114
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +381
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +181
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
+173
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection) +133
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject) +494
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(Htt pContext context,
Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConne ction(String
connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUse r(String username) +771
System.Web.Security.RolePrincipal.IsInRole(String role) +272
loginredirect.Page_Load(Object sender, EventArgs e) in
d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb:6
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433;
ASP.NET Version:2.0.50727.1433
Jun 27 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
By default SQl2005 does not accept remote connections e.g when they are made
with remote IP (not with local IP address). E.g first check that you have
correct IP.

This remote connection allowing is configured with SQL Server's Surface
Area configuration tool (there are selections Local connections Only/Local
and remote connections). In case this isn't something you can control, I
suggest you contact your host

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke

"Cirene" <ci****@nowhere.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
>I just deployed my new ASP.NET (3.5 FW) site to the hosting company I'm
using, webhost4life.

NOTE: I HAVE deployed other SQL Server sites to the same account with no
issues.

Now I'm getting this error. Any idea why?

Server Error in '/myuser4/MyWebApp' Application.
--------------------------------------------------------------------------------

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: 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)

Source Error:
Line 4:
Line 5: Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
Line 6: If User.IsInRole("LexAdmin") Or
User.IsInRole("LexOperator") Or User.IsInRole("LexUser") Then
Line 7: Response.Redirect("admin/ManagePackages.aspx")
Line 8: ElseIf User.IsInRole("CustomerAdmin") Or
User.IsInRole("CustomerClient") Or User.IsInRole("CustomerUser") Then
Source File: d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb
Line: 6

Stack Trace:
[SqlException (0x80131904): 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)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection) +800131

System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj) +186
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject) +737554

System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject) +114
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
+381

System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +181

System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String newPassword, SqlConnection owningObject, Boolean
redirectedUserInstance) +173

System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection) +133

System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject) +494
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(Htt pContext context,
Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConne ction(String
connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUse r(String username)
+771
System.Web.Security.RolePrincipal.IsInRole(String role) +272
loginredirect.Page_Load(Object sender, EventArgs e) in
d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb:6
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433;
ASP.NET Version:2.0.50727.1433

Jun 27 '08 #2

P: n/a
the error means that connection to the sqlserver could not be made (name
resolution or socket open failed). assuming the sqlserver is configured,
either you have the connection string wrong (name and port number) or the
network is blocking the connection (firewall rules).

-- bruce (sqlwork.com)
"Cirene" wrote:
I just deployed my new ASP.NET (3.5 FW) site to the hosting company I'm
using, webhost4life.

NOTE: I HAVE deployed other SQL Server sites to the same account with no
issues.

Now I'm getting this error. Any idea why?

Server Error in '/myuser4/MyWebApp' Application.
--------------------------------------------------------------------------------

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: 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)

Source Error:
Line 4:
Line 5: Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
Line 6: If User.IsInRole("LexAdmin") Or
User.IsInRole("LexOperator") Or User.IsInRole("LexUser") Then
Line 7: Response.Redirect("admin/ManagePackages.aspx")
Line 8: ElseIf User.IsInRole("CustomerAdmin") Or
User.IsInRole("CustomerClient") Or User.IsInRole("CustomerUser") Then
Source File: d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb
Line: 6

Stack Trace:
[SqlException (0x80131904): 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)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection) +800131
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj) +186
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject) +737554
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject) +114
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +381
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +181
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
+173
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection) +133
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject) +494
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(Htt pContext context,
Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConne ction(String
connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUse r(String username) +771
System.Web.Security.RolePrincipal.IsInRole(String role) +272
loginredirect.Page_Load(Object sender, EventArgs e) in
d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb:6
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433;
ASP.NET Version:2.0.50727.1433
Jun 27 '08 #3

P: n/a
From error "...provider: Named Pipes Provider" I understand that you using
Named Pipes protocol and not TCP/IP.

Named pipes protocol works well only in Domain environment.
It has embedded NT authentication. So if guest account disabled on the
server then Named pipes connection will be refused.

You need to switch it to TCP/IP
Try to add "Network Library=DBMSSOCN" to your connection string
"Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial
Catalog=myDataBase;User ID=myUsername;Password=myPassword;"

George.
"bruce barker" <br*********@discussions.microsoft.comwrote in message
news:EC**********************************@microsof t.com...
the error means that connection to the sqlserver could not be made (name
resolution or socket open failed). assuming the sqlserver is configured,
either you have the connection string wrong (name and port number) or the
network is blocking the connection (firewall rules).

-- bruce (sqlwork.com)
"Cirene" wrote:
>I just deployed my new ASP.NET (3.5 FW) site to the hosting company I'm
using, webhost4life.

NOTE: I HAVE deployed other SQL Server sites to the same account with no
issues.

Now I'm getting this error. Any idea why?

Server Error in '/myuser4/MyWebApp' Application.
--------------------------------------------------------------------------------

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: 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)

Source Error:
Line 4:
Line 5: Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
Line 6: If User.IsInRole("LexAdmin") Or
User.IsInRole("LexOperator") Or User.IsInRole("LexUser") Then
Line 7: Response.Redirect("admin/ManagePackages.aspx")
Line 8: ElseIf User.IsInRole("CustomerAdmin") Or
User.IsInRole("CustomerClient") Or User.IsInRole("CustomerUser") Then
Source File: d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb
Line: 6

Stack Trace:
[SqlException (0x80131904): 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)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection) +800131

System.Data.SqlClient.TdsParser.ThrowExceptionAnd Warning(TdsParserStateObject
stateObj) +186
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject) +737554

System.Data.SqlClient.SqlInternalConnectionTds.At temptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject) +114
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
+381

System.Data.SqlClient.SqlInternalConnectionTds.Op enLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +181

System.Data.SqlClient.SqlInternalConnectionTds..c tor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
+173

System.Data.SqlClient.SqlConnectionFactory.Create Connection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection
owningConnection) +133

System.Data.ProviderBase.DbConnectionFactory.Crea tePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject) +424

System.Data.ProviderBase.DbConnectionPool.UserCre ateRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject) +494

System.Data.ProviderBase.DbConnectionFactory.GetC onnection(DbConnection
owningConnection) +82

System.Data.ProviderBase.DbConnectionClosed.OpenC onnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(Htt pContext context,
Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConne ction(String
connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUse r(String username)
+771
System.Web.Security.RolePrincipal.IsInRole(String role) +272
loginredirect.Page_Load(Object sender, EventArgs e) in
d:\hosting\member\myuser4\MyWebApp\loginredirect. aspx.vb:6
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+1436


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433;
ASP.NET Version:2.0.50727.1433

Jun 27 '08 #4

P: n/a
I'm using the exact connection string (different db of course) of other
websites that ARE working.

Is this wierd? Any more ideas?

Thanks!

"bruce barker" <br*********@discussions.microsoft.comwrote in message
news:EC**********************************@microsof t.com...
the error means that connection to the sqlserver could not be made (name
resolution or socket open failed). assuming the sqlserver is configured,
either you have the connection string wrong (name and port number) or the
network is blocking the connection (firewall rules).

-- bruce (sqlwork.com)
"Cirene" wrote:
>I just deployed my new ASP.NET (3.5 FW) site to the hosting company I'm
using, webhost4life.

NOTE: I HAVE deployed other SQL Server sites to the same account with no
issues.

Now I'm getting this error. Any idea why?

Server Error in '/myuser4/MyWebApp' Application.
--------------------------------------------------------------------------------

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: 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)

Source Error:
Line 4:
Line 5: Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
Line 6: If User.IsInRole("LexAdmin") Or
User.IsInRole("LexOperator") Or User.IsInRole("LexUser") Then
Line 7: Response.Redirect("admin/ManagePackages.aspx")
Line 8: ElseIf User.IsInRole("CustomerAdmin") Or
User.IsInRole("CustomerClient") Or User.IsInRole("CustomerUser") Then
Source File: d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb
Line: 6

Stack Trace:
[SqlException (0x80131904): 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)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection) +800131

System.Data.SqlClient.TdsParser.ThrowExceptionAnd Warning(TdsParserStateObject
stateObj) +186
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject) +737554

System.Data.SqlClient.SqlInternalConnectionTds.At temptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject) +114
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
+381

System.Data.SqlClient.SqlInternalConnectionTds.Op enLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +181

System.Data.SqlClient.SqlInternalConnectionTds..c tor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
+173

System.Data.SqlClient.SqlConnectionFactory.Create Connection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection
owningConnection) +133

System.Data.ProviderBase.DbConnectionFactory.Crea tePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject) +424

System.Data.ProviderBase.DbConnectionPool.UserCre ateRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject) +494

System.Data.ProviderBase.DbConnectionFactory.GetC onnection(DbConnection
owningConnection) +82

System.Data.ProviderBase.DbConnectionClosed.OpenC onnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(Htt pContext context,
Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConne ction(String
connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUse r(String username)
+771
System.Web.Security.RolePrincipal.IsInRole(String role) +272
loginredirect.Page_Load(Object sender, EventArgs e) in
d:\hosting\member\myuser4\MyWebApp\loginredirect. aspx.vb:6
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+1436


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433;
ASP.NET Version:2.0.50727.1433

Jun 27 '08 #5

P: n/a
Hello Cirene,

I have had similar experience with 1and1.com.

I had a hosting account with them and decided to connect my application that
was hosted somewhere else to the sql server database i have with them.

The application could not connect to the sql server db. Some hosting may
require that your application be hosted on their enviroment before you can
access the sql server database.

You can also check how you're managing the roles. Are you using an attached
database to manage the roles? If yes, you have to grant ASP.NET access to the
folder containing the database file.

Thank you,
Okoronkwo Alfred Chinedu
--
Okoronkwo Chinedu
Crazy About Learning
"Cirene" wrote:
I'm using the exact connection string (different db of course) of other
websites that ARE working.

Is this wierd? Any more ideas?

Thanks!

"bruce barker" <br*********@discussions.microsoft.comwrote in message
news:EC**********************************@microsof t.com...
the error means that connection to the sqlserver could not be made (name
resolution or socket open failed). assuming the sqlserver is configured,
either you have the connection string wrong (name and port number) or the
network is blocking the connection (firewall rules).

-- bruce (sqlwork.com)
"Cirene" wrote:
I just deployed my new ASP.NET (3.5 FW) site to the hosting company I'm
using, webhost4life.

NOTE: I HAVE deployed other SQL Server sites to the same account with no
issues.

Now I'm getting this error. Any idea why?

Server Error in '/myuser4/MyWebApp' Application.
--------------------------------------------------------------------------------

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: 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)

Source Error:
Line 4:
Line 5: Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
Line 6: If User.IsInRole("LexAdmin") Or
User.IsInRole("LexOperator") Or User.IsInRole("LexUser") Then
Line 7: Response.Redirect("admin/ManagePackages.aspx")
Line 8: ElseIf User.IsInRole("CustomerAdmin") Or
User.IsInRole("CustomerClient") Or User.IsInRole("CustomerUser") Then
Source File: d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb
Line: 6

Stack Trace:
[SqlException (0x80131904): 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)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection) +800131

System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj) +186
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject) +737554

System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject) +114
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
+381

System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +181

System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
+173

System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection
owningConnection) +133

System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30
System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject) +424

System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject) +494

System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection) +82

System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(Htt pContext context,
Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConne ction(String
connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUse r(String username)
+771
System.Web.Security.RolePrincipal.IsInRole(String role) +272
loginredirect.Page_Load(Object sender, EventArgs e) in
d:\hosting\member\myuser4\MyWebApp\loginredirect.a spx.vb:6
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+1436


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433;
ASP.NET Version:2.0.50727.1433


Jun 27 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.