connection string

mary.a.b · Mar 28, 2008

The old version of my application wasbuilt ona sql express database, which ran just fine on discount asp sql 2005. Now, the new version was built locally on a sql 2005 database. Today, I overwrote the old database with the new one, using the same sql 2005 acct., and I can connect to the newdatabase from my sql server mgmt studio - it is indeed there. however, when I try to log into the database from my web application, I get the error below - where did I go astray? I am using the connection string from my sql mgmt panel.

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: 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:
Code:
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:
Code:
[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) +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) +421
   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.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47
   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(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.SetupApplicationServices(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.CreateMdfFile(String fullFileName, String dataDir, String connectionString) +397
Version Information:Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

wisemx · Mar 28, 2008

Hi,
Post the connections part of your root web.config, make sure you comment out the password.
All the best,
Mark

mary.a.b · Mar 28, 2008

Here is the connection string below. I am wondering if I went astray
when I uploaded the detacheddatabase file into App_Data?
The instructions say to upload it to your website, but they don't say where.

Iamnot using sql express. Last year, when I first set this up, I was using sql express.

<add name="datacollectConnectionString" connectionString="Data Source=tcp:sql2k502.discountasp.net;Initial Catalog=SQL2005_222395_alwaysthere;User ID=SQL2005_222395_alwaysthere_user;Password=********;" providerName="System.Data.SqlClient"/>

Thanks for any help...

Aristotle · Apr 2, 2008

Are you sure the application is using that specific connection string name? It is probably using the default 'LocalSqlServer' connection string, which is pre-defined globally to connect to a SQL Express database. Try one of the following:

1. Change the name to 'LocalSqlServer'. You need to remove it first.

<removename='LocalSqlServer'/>
<addname='LocalSqlServer'connectionString='DataSource=tcp:sql2k502.discountasp.net;InitialCatalog=SQL2005_222395_alwaysthere;UserID=SQL2005_222395_alwaysthere_user;Password=********;'providerName='System.Data.SqlClient'/>
</CODE>

2. Change the app to use 'datacollectConnectionString'.

Aristotle

DiscountASP.NET
www.DiscountASP.NET
Click to expand...

pemurray · Apr 29, 2008

Sorry, I am having similar trouble and think it may be a connection string problem.

My application also has a special connection string name.

So I changed the connection string name to LocalSqlServer (along with the delete name tag and the add name tag)

But what is confusing is that in the last post in step 2, it is suggested that you use the connection string name that is no longer being referenced.

Of course, I am shooting in the dark a bit because I can't see the error because I am running it hosted. Anyone know how to 'see' what the actual error is?

Thank you,

Paul

wisemx · Apr 29, 2008

Show errors with settings inyour web.config:
http://weblogs.asp.net/scottgu/archive/2006/08/12/Tip_2F00_Trick_3A00_-Show-Detailed-Error-Messages-to-Developers.aspx

As for the connection names you can add more than one.
The reason LocalSqlServer is often used/included is it is often a default instance name.

Make sure you use clear first then add and remove any connection string names, like this:

<connectionStrings>
<clear/>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="Data Source=tcp:sql.discountasp.net;Initial Catalog=SQLdb;User ID=SQL_user;Password=ChangeMe;" providerName="System.Data.SqlClient"/>
<remove name="SQL_userConnectionString"/>
<add name="SQL_userConnectionString" connectionString="Data Source=tcp:sql.discountasp.net;Initial Catalog=SQLdb;User ID=SQL_user;Password=ChangeMe;" providerName="System.Data.SqlClient"/>
</connectionStrings>

Hope that helps.
Salute,
Mark

Log in or Sign up

connection string

mary.a.b

wisemx

mary.a.b

Aristotle

pemurray

wisemx

Share This Page

Log in or Sign up

connection string

mary.a.b

wisemx

mary.a.b

Aristotle

pemurray

wisemx

Share This Page

Useful Searches