Funny Error

[Chris Love]

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)

I get this the frist time I open an ASP.NEt 2.0 site on my development
machine now. It started happening when I tried to use the Membership
Provider for the first time.

How do I fix this. It takes 60 seconds for this to time out before I can
start debugging now. That is a good 30 minutes a day I have to waste.

[Chris Love]

I have SQL 2000 installed. This only happens when I start up the site. if I
hit refresh everything works fine.

"Spam Catcher" wrote:

"=?Utf-8?B?Q2hyaXMgTG92ZQ==?=" <Ch*******@discussions.microsoft.com>
wrote in news:52**********************************@microsof t.com:

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)

Do you happen to have SQL Server 2000 installed?

Perhaps SQL Server 2005 is not bound to the TCP port? That can happen if
there is another program using TCP Port 1433.

--
Stan Kee (sp**********@rogers.com)

[mablejune]

On Fri, 16 Dec 2005 17:46:18 -0800, "Chris Love"
<Ch*******@discussions.microsoft.com> wrote:

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)

I get this the frist time I open an ASP.NEt 2.0 site on my development
machine now. It started happening when I tried to use the Membership
Provider for the first time.

How do I fix this. It takes 60 seconds for this to time out before I can
start debugging now. That is a good 30 minutes a day I have to waste.

Go to the SQL server Configurator (or some name like that). You will
need to turn on TCPIP (turned off by default. That will fix the
problem.

[Chris Love]

TCP/IP and Named Pipes Libraries are enabled.

This only started after I tried to use the membership provder through the
web administration interface of VS 2005. It could not configure it for my
site's database for some reasone and then this started. Everything was fine
before that.

"ma*******@otismukinfus.com" wrote:

On Fri, 16 Dec 2005 17:46:18 -0800, "Chris Love"
<Ch*******@discussions.microsoft.com> wrote:

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)

I get this the frist time I open an ASP.NEt 2.0 site on my development
machine now. It started happening when I tried to use the Membership
Provider for the first time.

How do I fix this. It takes 60 seconds for this to time out before I can
start debugging now. That is a good 30 minutes a day I have to waste.

Go to the SQL server Configurator (or some name like that). You will
need to turn on TCPIP (turned off by default. That will fix the
problem.

[Chris Love]

Still getting the error. Since the MS team is supposed to respond within 72
hours, I expect the answer sometime today.

"Chris Love" wrote:

TCP/IP and Named Pipes Libraries are enabled.

This only started after I tried to use the membership provder through the
web administration interface of VS 2005. It could not configure it for my
site's database for some reasone and then this started. Everything was fine
before that.

"ma*******@otismukinfus.com" wrote:

On Fri, 16 Dec 2005 17:46:18 -0800, "Chris Love"
<Ch*******@discussions.microsoft.com> wrote:

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)

I get this the frist time I open an ASP.NEt 2.0 site on my development
machine now. It started happening when I tried to use the Membership
Provider for the first time.

How do I fix this. It takes 60 seconds for this to time out before I can
start debugging now. That is a good 30 minutes a day I have to waste.

Go to the SQL server Configurator (or some name like that). You will
need to turn on TCPIP (turned off by default. That will fix the
problem.

[Tony Dong]

try to run

1. c:\windows\microsoft.net\framework\v2.0.5xxx> aspnet_regsql.exe

may it will solve your problem, I solve my problem using this way.

Tony Dong

"Chris Love" <Ch*******@discussions.microsoft.com> wrote in message
news:24**********************************@microsof t.com...

Still getting the error. Since the MS team is supposed to respond within
72
hours, I expect the answer sometime today.

"Chris Love" wrote:

TCP/IP and Named Pipes Libraries are enabled.

This only started after I tried to use the membership provder through the
web administration interface of VS 2005. It could not configure it for
my
site's database for some reasone and then this started. Everything was
fine
before that.

"ma*******@otismukinfus.com" wrote:

> On Fri, 16 Dec 2005 17:46:18 -0800, "Chris Love"
> <Ch*******@discussions.microsoft.com> wrote:
>
> >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)
> >
> >I get this the frist time I open an ASP.NEt 2.0 site on my development
> >machine now. It started happening when I tried to use the Membership
> >Provider for the first time.
> >
> >How do I fix this. It takes 60 seconds for this to time out before I
> >can
> >start debugging now. That is a good 30 minutes a day I have to waste.
>
> Go to the SQL server Configurator (or some name like that). You will
> need to turn on TCPIP (turned off by default. That will fix the
> problem.
>

[Chris Love]

Nope, this did not fix the problem:

Server Error in '/YourSellPro' 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified)
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.

SQLExpress database file auto-creation error:
The connection string specifies a local Sql Server Express instance using a
database location within the applications App_Data directory. The provider
attempted to automatically create the application services database because
the provider determined that the database does not exist. The following
configuration requirements are necessary to successfully check for existence
of the application services database and automatically create the application
services database:
If the applications App_Data directory does not already exist, the web
server account must have read and write access to the applications directory.
This is necessary because the web server account will automatically create
the App_Data directory if it does not already exist.
If the applications App_Data directory already exists, the web server
account only requires read and write access to the applications App_Data
directory. This is necessary because the web server account will attempt to
verify that the Sql Server Express database already exists within the
applications App_Data directory. Revoking read access on the App_Data
directory from the web server account will prevent the provider from
correctly determining if the Sql Server Express database already exists. This
will cause an error when the provider attempts to create a duplicate of an
already existing database. Write access is required because the web server
accounts credentials are used when creating the new database.
Sql Server Express must be installed on the machine.
The process identity for the web server account must have a local user
profile. See the readme document for details on how to create a local user
profile for both machine and domain accounts.
Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

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.OnErro r(SqlException
exception, Boolean breakConnection) +734787

System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
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.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance) +628

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

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

System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection) +47
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.Management.SqlServices.GetSqlConnection (String server, String
user, String password, Boolean trusted, String connectionString) +68

[HttpException (0x80004005): Unable to connect to SQL Server database.]
System.Web.Management.SqlServices.GetSqlConnection (String server, String
user, String password, Boolean trusted, String connectionString) +124
System.Web.Management.SqlServices.SetupApplication Services(String server,
String user, String password, Boolean trusted, String connectionString,
String database, String dbFileName, SqlFeatures features, Boolean install) +86
System.Web.Management.SqlServices.Install(String database, String
dbFileName, String connectionString) +25
System.Web.DataAccess.SqlConnectionHelper.CreateMd fFile(String
fullFileName, String dataDir, String connectionString) +397


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