A network-related or instance-specific error occurred while establishing a connection

Discussion in 'Databases' started by froutoneagr, Jul 28, 2009.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Hello to all,
    Every time i run my application i receive this message,

    Server Error in '/' Application.

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    [FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif] 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:

    [/FONT][FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif]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:
    [/FONT]

    1. [FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif][/FONT][FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif]
    2. 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.
    3. 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.
    4. Sql Server Express must be installed on the machine.
    5. 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.[/FONT]
    [FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif]

    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): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
    System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4846887
    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
    System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +4860189
    System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +90
    System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +376
    System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +221
    System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +189
    System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +4861315
    System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +29
    System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +4863644
    System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
    System.Data.SqlClient.SqlConnection.Open() +122
    System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +82

    [HttpException (0x80004005): Unable to connect to SQL Server database.]
    System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +137
    System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +94
    System.Web.Management.SqlServices.Install(String database, String dbFileName, String connectionString) +25
    System.Web.DataAccess.SqlConnectionHelper.CreateMdfFile(String fullFileName, String dataDir, String connectionString) +395

    [/FONT] [FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif] Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082


    THE Wierh thing is this application runs perfect from my PC (Dev studio 2008) by opening connection with ASP NET Discount Connection string. So Connection String is ok.
    <add connectionString="Data Source=tcp:esql2k502.discountasp.net;Initial Catalog=SQL2005_639445_froutonea;User ID=SQL2005_639445_froutonea_user;Password=*;" name="defaultconnection"/>

    In my application i use LINQ to SQL Classes and the most funny is that for testing purpose i put in the front aspx file (default.aspx) the folowing code, which worked fine

    1) open connection (ok)
    2) open connection with LINQ (ok)
    3) fetch data from table (ok) .

    But when i run my application i receive the above error
    ... i cant figure out where else to search.

    And why is says [/FONT][FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif]SQLExpress database file auto-creation error: ???

    I dont use SQLExpress database ! i bought SQL Server 2005

    Any help or idea is appreciated ..
    Thanks in advance
    [/FONT][FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif]
    [/FONT]
     
  2. Hi,
    Try configuring your web.config like the example below to override the default Express instance and to clear out anything that may be causing trouble.

    <connectionStrings>
    <clear />
    <remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=tcp:sql2k5.discountasp.net;Initial Catalog=SQL2005_msftwise;User ID=SQL2005_msftwise_user;Password=****" providerName="System.Data.SqlClient" />
    <remove name="SQL2005_msftwise_userConnectionString"/>
    <add name="SQL2005_msftwise_userConnectionString" connectionString="Data Source=tcp:sql2k.discountasp.net;Initial Catalog=SQL2005_msftwise;Persist Security Info=True;User ID=SQL2005_msftwise_user;Password=****" providerName="System.Data.SqlClient" />
    <remove name="SQL2008_msftwise_userConnectionString"/>
    <add name="SQL2008_msftwise_userConnectionString" connectionString="Data Source=tcp:sql2k8.discountasp.net;Initial Catalog=SQL2008_wisemx;Persist Security Info=True;User ID=SQL2008_wisemx_user;Password=****" providerName="System.Data.SqlClient" />
    </connectionStrings>
     

  3. Thank you very much for your quick reply. I tried the following...

    i changed connection string to
    <clear />
    <remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=tcp:esql2k502.discountasp.net;Initial Catalog=SQL2005_639445_froutonea;User ID=SQL2005_639445_froutonea_user;Password=**" providerName="System.Data.SqlClient" />
    <remove name="defaultconnection"/>
    <add connectionString="Data Source=tcp:esql2k502.discountasp.net;Initial Catalog=SQL2005_639445_froutonea;Persist Security Info=True;User ID=SQL2005_639445_froutonea_user;Password=**;" providerName="System.Data.SqlClient" name="defaultconnection"/>
    </connectionStrings>


    and i have the message now
    Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.


    by changing the connection string to :

    <connectionStrings>
    <clear />
    <remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=tcp:sql2k5.discountasp.net;Initial Catalog=SQL2005_msftwise;User ID=SQL2005_639445_froutonea_user;Password=**" providerName="System.Data.SqlClient" />
    <remove name="defaultconnection"/>
    <add connectionString="Data Source=tcp:esql2k502.discountasp.net;Initial Catalog=SQL2005_639445_froutonea;Persist Security Info=True;User ID=SQL2005_639445_froutonea_user;Password=**;" providerName="System.Data.SqlClient" name="defaultconnection"/>
    </connectionStrings>

    i have the message :
    Server Error in '/' Application.

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.)


    Can you please be more specific? should i keep all your connection string struct, like username and Data Source and Initial Catalog ?

    Thank you very much in advance. :eek::eek:



     
  4. Actually i need to deploy the application and i am stuck to this error. As far as i google it, the problem seems to be that a misconfiguration took place in froutonea.gr.

    Please advice me what to do ASAP.
     
  5. ...I'm a bit lost, does it seem you have a connection now but some DB objects are missing?
    If so, what are you using to sync your data?
    All the best,
    Mark
     
  6. Mark, Thank you for your response and concern,

    The problem appears when i execute my application, probably the first time it tries to do some session stuff.

    check out at : www.froutonea.gr/default.aspx

    without this in my connection string
    clear />
    <remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=tcp:esql2k502.discountasp.net;Initial Catalog=SQL2005_639445_froutonea;User ID=SQL2005_639445_froutonea_user;Password=**" providerName="System.Data.SqlClient" />

    the application returns an error of [FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif]SQLExpress database file auto-creation error:

    and when i put it, the message is
    [/FONT]Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

    And of course to remind you that this project runs fine from my PC using the discount asp net connection string. (eg. database on Internet and application in local IIS) but after publish through ftp, when it runs from internet it returns those errors.

    All those messages have to do with aspnet auto created tables either in SQL Express or SQL (by defining so).
    Maybe in the sql server you haven't run aspnet_regsql,

    I don't know.

    Sorry for my bad English.

    Best Regards
     
  7. ...You're doing fine with English..Mein Deutsch ist schlecht ;-)

    Yes this can create problems if the Membership registration was not run against the remote server.
    I created a Webcast on this last year recommending to run the command locally but against the remote server. http://www.dasptv.com/

    This appears to be what is happening and I do suspect your connection is working when you get the Stored Procedure error.

    I'd recommend starting over if you can, create the Membership roles as in the Webcast, not with the ASP.NET Wizard, then publish nay additional DB tables and records.
    All the best,
    Mark
     
  8. Your Web cast was very Helpfull and now my application runs fine !! :)

    Although the question remains, why the Sql Express automated function didn't work out for me? The memberships should be in my SQL server and not on asp.net sql Express?

    Anyway aspnet_regsql made the trick, everything seems smooth.
    :)
    Thank you very much Mark !
     
  9. ...Nice ;-)

    I can't explain everything but one of my favorite quotes sums it up:

    "You do not really understand something unless you can explain it to your grandmother."
    Albert Einstein.
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page