Re: Error "SQL Server does not allow remote connections"
- From: ChigbuaUmuenu <ChigbuaUmuenu@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 24 May 2008 07:24:18 -0700
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" <brucebarker@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EC7F21EE-B8E2-4F46-8ED6-8E1FB7383CAB@xxxxxxxxxxxxxxxx
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.aspx.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.OnError(SqlException
exception, Boolean breakConnection) +800131
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(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.AttemptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject) +114
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
+381
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +181
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
+173
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection
owningConnection) +133
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject) +494
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context,
Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConnection(String
connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUser(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
- References:
- Error "SQL Server does not allow remote connections"
- From: Cirene
- RE: Error "SQL Server does not allow remote connections"
- From: bruce barker
- Re: Error "SQL Server does not allow remote connections"
- From: Cirene
- Error "SQL Server does not allow remote connections"
- Prev by Date: Is there a way to remove Application Services from the config?
- Next by Date: Is LocalSqlServer necessary for web.config connection string???
- Previous by thread: Re: Error "SQL Server does not allow remote connections"
- Next by thread: # NET 2.0 developers needed
- Index(es):
Relevant Pages
|
|
