 Rank: Newbie
Groups: Member
Joined: 1/2/2007(UTC)
Posts: 1
Location: Ca
|
HI all,
Any Idea how to solve this problem:
Steps have taken:
I enabled the TCP/IP for remote connection.
but I have this problem:
Server Error in '/' 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)
|
|
|
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/31/2006(UTC)
Posts: 40
Location: Nottingham, UK
|
try this:
(i'm assuming your not on a hostingfest shared plan?)
Eventually after a timeout delay I ended up with a connection error message that says:
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) (Microsoft SQL Server, Error: 2)
A couple of searches through the Properties of the server didn't show anything refusing connections – the connection count is set to 0 (unlimited connections) and this would be the logical spot to find an option that refuses connections, right?
Well, it turns out that this is controlled by an EXTERNAL utility, the Sql Server Surface Area Configuration Tool which can be found in Start Menu Sql Server Configuration section. By default Sql 2005 indeed refuses remote connections and you need to run this utility to enable remote connections. Intuitive isn't it?
|
|
|
|
|
|
 Rank: Administration
Groups: Administration, Member Joined: 1/3/2006(UTC) Posts: 348  Was thanked: 1 time(s) in 1 post(s)
|
khalid wrote:HI all,
Any Idea how to solve this problem:
Steps have taken:
I enabled the TCP/IP for remote connection.
but I have this problem:
Server Error in '/' 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)
If you don't know the IP for the SQL server open a ticket and we will let you know. This problem is either due to wrong IP address or a local firewall or even an antivirus. |
Noman Dormosh
HostingFest |
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The HostingFest Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
