failed to connect to new instance in MSSQL2005

I tried to connect to a new created instance (specifying server\instance)in
MSSQL2005 server with mangement studio in another mssql2005 server. It show
an 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instanc
e
Specified) (.Net SqlClient Data Provider)'
I have enabled the TCPIP in configuration manager and with allow remote
access enabled.
Any idea on it? Thanks in advance!Hello,
could be the following:
http://support.microsoft.com/defaul...kb;en-us;307197
regards,
Henk
"stephanie" <stephanie@.discussions.microsoft.com> wrote in message
news:2BD93101-CA8A-47A4-A766-DDC090C9AD5D@.microsoft.com...
>I tried to connect to a new created instance (specifying server\instance)in
> MSSQL2005 server with mangement studio in another mssql2005 server. It
> show
> an 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance
> Specified) (.Net SqlClient Data Provider)'
> I have enabled the TCPIP in configuration manager and with allow remote
> access enabled.
> Any idea on it? Thanks in advance!
>|||Could be blocked by the firewall, particularly if the SQL Server is running
on Windows XP Professional SP1.
Could be unable to get the port number of the named instance because the SQL
Server Browser Service (on the server computer) is not running, or is
blocked by the firewall.
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx has a
step by step review of some common connectivity issues.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Henk Steunenberg (Ms)" <stjesp@.hotmail.com> wrote in message
news:OFRCwrWLGHA.1180@.TK2MSFTNGP09.phx.gbl...
> Hello,
> could be the following:
> http://support.microsoft.com/defaul...kb;en-us;307197
> regards,
> Henk
> "stephanie" <stephanie@.discussions.microsoft.com> wrote in message
> news:2BD93101-CA8A-47A4-A766-DDC090C9AD5D@.microsoft.com...
>|||Thanks for all's reply.
I have studied through the suggestion material and configured in SQL2005 but
the same error is still occur.
While I telnet to servernname with named instance port #, it success.
Any other advise. Thanks in advance!
"Rick Byham [MS]" wrote:

> Could be blocked by the firewall, particularly if the SQL Server is runnin
g
> on Windows XP Professional SP1.
> Could be unable to get the port number of the named instance because the S
QL
> Server Browser Service (on the server computer) is not running, or is
> blocked by the firewall.
> http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx has a
> step by step review of some common connectivity issues.
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Documentation Manager,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "Henk Steunenberg (Ms)" <stjesp@.hotmail.com> wrote in message
> news:OFRCwrWLGHA.1180@.TK2MSFTNGP09.phx.gbl...
>
>|||I have enabled the service 'SQL Server Browers' and now it works
"stephanie" wrote:
[vbcol=seagreen]
> Thanks for all's reply.
> I have studied through the suggestion material and configured in SQL2005 b
ut
> the same error is still occur.
> While I telnet to servernname with named instance port #, it success.
> Any other advise. Thanks in advance!
> "Rick Byham [MS]" wrote:
>|||Right. The SQL Server Browser Service receives requests for named instances
and responds with the port number that the instance is listening on. Then
the SQL Server Native Client talks directly to the port.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"stephanie" <stephanie@.discussions.microsoft.com> wrote in message
news:146E8DB0-DB1E-4C8B-8DF0-C30737B4692E@.microsoft.com...[vbcol=seagreen]
>I have enabled the service 'SQL Server Browers' and now it works
> "stephanie" wrote:
>|||I have exactly the same problem (see below)
I've enabled TCP/IP, enabled browser service, made sure there is no error in
binding to TCP/IP via the SQL logs. Still I keep getting the same error.
Any clue'
I have the following setup:
1. ASP.NET 2.0 web app hosted on a web server (inetpub directory
hosting physical files of the web site on a different drive name, E:
than the SQL Server Instance, which is on C
2. SQL Server on the same server, with security settings enabling
ASPNET group and groups containing users allowed to interact with the
website added to SQL Server Instance security settings.
3. Impersonation = true, i.e. ASPNET worker process will impersonate
the user who has been authenticated by IIS
I am continiously getting 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: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)
The stack trace and event log is at the end of this post.
I tried the following:
1. enabled TCPIP and Pipes for remote connection via the SQL Server
Configuration Manager
2. enabled remote and local connections via the SQL Surface area
Configuration (TCPIP and named pipes)
3. totally disabled the firewall (even if it is enabled, both the
sqlbrowser, and sqlserver are added as exceptions)
4. enabled the SQL Server Browser Service (to start automatically)
I've tried doing everything i came across on the net.
Nobody seems to have a solution but a lot of people have encountered
this problem.
If anybody out there does have a solution, PLEASE reply to this post.
Thanking you in advance
Part of the 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: SQL Network
Interfaces, error: 26 - Error Locating Server/Instance Specified)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection) +734995
System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
bje
_ct
stateObj) +188
System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
Boolean& failoverDemandDone, String host, String failoverPartner,
String protocol, SqlInternalConnectionTds connHandler, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
+820
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnectio
_n
owningObject, SqlConnectionString connectionOptions, String
newPassword, Boolean redirectedUserInstance) +628
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdenti
_ty
identity, SqlConnectionString connectionOptions, Object providerInfo,
String newPassword, SqlConnection owningObject, Boolean
redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOpt
_ions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection owningConnection) +130
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConne
_ction
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
+28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject) +496
Part of the Event Log (Application)
---
Process information:
Process ID: 5600
Process name: w3wp.exe
Account name: EUSRCMW309\IWAM_EUSRCMW309
Exception information:
Exception type: SqlException
Exception message: 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: SQL Network
Interfaces, error: 26 - Error Locating Server/Instance Specified)
Request information:
Request URL: http://138.85.90.253/psdb/main.aspx
Request path: /psdb/main.aspx
User host address: 138.85.90.253
User: EAMCS\EUSJESadm
Is authenticated: True
Authentication Type: Negotiate
Thread account name: EUSRCMW309\IWAM_EUSRCMW309
"Rick Byham [MS]" wrote:

> Right. The SQL Server Browser Service receives requests for named instance
s
> and responds with the port number that the instance is listening on. Then
> the SQL Server Native Client talks directly to the port.
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Documentation Manager,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "stephanie" <stephanie@.discussions.microsoft.com> wrote in message
> news:146E8DB0-DB1E-4C8B-8DF0-C30737B4692E@.microsoft.com...
>
>