An attempt to attach an auto-named database ....\aspnetdb.mdf failed

SQL Server Database Engine

mfauziii


I've installed VWD 2005(Beta 2) and MS SQL Express and also followed the aspnet tour at http://beta.asp.net/guidedtour2. After trying new webcontrol (login control) and trying to execute the page, I've got an error such as below:

An attempt to attach an auto-named database for file c:\inetpub\wwwroot\Demo\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.


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 attempt to attach an auto-named database for file c:\inetpub\wwwroot\Demo\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

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 attempt to attach an auto-named database for file c:\inetpub\wwwroot\Demo\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +684979 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +207 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1751 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +32 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +601 System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +159 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +346 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +445 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +304 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +85 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +126 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +239 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved) +815 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +80 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +78 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +161 System.Web.UI.WebControls.Login.AttemptLogin() +94 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +101 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +134 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5670
 

 


can anyone help me to solve the problem... thanks

Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Boris B


Please take a look at the following post:

http://forums.microsoft.com/msdn/ShowPost.aspx PostID=98346 

and see if the explanation there helps you to solve the problem.

Regards,
Boris.




Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Eckmar

But it's impossible to find the right solution in the forum. A lot of developers with the same problem and no real successful answer. The problem is not only in the beta products, it's still in the release version. In my case I took a web project working fine from one PC to another, copy the files change all relevant path entries and nothing goes anymore with the database files. Even not when trying to run the files on a SQL 2005 Developer Server.

Trying over a weekend and still no solution (even after new installation of the SQL servers).

Best regards,

Eckmar





Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Powermax

What configuration do you have for aspnetdb.mdf in properties You must set Copy to output: Copy if newer or Copy always. I recommended Copy if newer.

Regards


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Chris B. Behrens

I recently encountered this when I tried to add role management to a successfully operating user db. I had a connectionstring with a db name specified. Why should it need to autoname, or attempt to auto-attach It must not be using the connectionstring I specified for the user db. I looked at the web config and the role manager entry was as follows;

<roleManager enabled="true" />

I modified it to be the following:

<roleManager enabled="true" defaultProvider="SqlRoleProvider">
<providers>
<clear/>
<add name="SqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="securityDB" />
</providers>
</roleManager>.

where securityDB was the connectionstring I was using for my DB. Made it work like a charm.

Hope this helps.


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Me Myself and I

Did you create this using Visual Web Developer Express or Full Visual Studio 2005

I tried this in Express and it couldn't connect to my DB





Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Me Myself and I

Here is a solution that I came up with...seeing as how most of the hosting solutions are shared IP, the SQLExpress will not be usable...therefore, you will have to create an SQL DB on your server...connect to it using the aspnet reqsql.exe to attach it to your app...write the connection string...set up the roles, users, etc with the aspnet configuration...and it works!!!

I would venture to say that the SQLExpress is only for Local Intranets, and web developer machines.





Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Dan Burnip

i had this same error, but it was due to me having an extra ODBC datasource (created by VISIO 2003) i believe. Fixed by; Goto Control Panel> admin tools> Datasources> File DSN tab then i deleted the overlapping datasource after 3 days of misery.


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

ShrinanD Vyas

Here is Permanent Solution of this Problem:

Point 1:
Make sure U have Database.mdf file under app_data directory if you are using |DataDirectory| in the Connection String.

Point 2:
string connstring = @"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Database.mdf;Integrated Security=True;User Instance=True";

I hope this will solve your Problem.

ShriannD
Uni of Houston


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

rookie.NET2005

In my case I had made a copy of a website, and both the old and new gave me that error on the development server for Visual Studio2005, perhaps because I made changes to the database. By renaming the database in each instance, and making sure the connection string (in web.config) pointed to the correct website and file I seemed to have solved the problem.rookie


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

porov

I had the same problem with my website freehosting1.net
What i did to resolve it was just to add the database property and delete the log file.
But anyway sqlserver has alot of problems with error messages, like in this case it doenst give you specific information on what you should do to resolve it.




Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

pekara

mfauziii wrote:

I've installed VWD 2005(Beta 2) and MS SQL Express and also followed the aspnet tour at http://beta.asp.net/guidedtour2. After trying new webcontrol (login control) and trying to execute the page, I've got an error such as below:

An attempt to attach an auto-named database for file c:\inetpub\wwwroot\Demo\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.


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 attempt to attach an auto-named database for file c:\inetpub\wwwroot\Demo\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

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 attempt to attach an auto-named database for file c:\inetpub\wwwroot\Demo\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +684979 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +207 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1751 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +32 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +601 System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +159 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +346 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +445 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +304 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +85 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +126 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +239 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved) +815 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +80 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +78 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +161 System.Web.UI.WebControls.Login.AttemptLogin() +94 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +101 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +134 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5670


can anyone help me to solve the problem... thanks


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

Dan Murphy At Trailmark

I received the same error while doing a tutorial. I had created my website under my user account located at C:\Documents and Settings\<your user account>\My Documents\Visual Studio 2005. This apparently caused a permissions error that I wasn't aware of. I moved the mdf and ldf file to the root c: and added "Everyone" to the permissions for the files. Then I modifed the web.config file connection string to hard code the path to the file as below. That got around the problem. That's not a long term solution but it allowed me to continue on with the tutorial.

<connectionStrings>

<add name="NORTHWNDConnectionString"

connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=c:\NORTHWND.MDF;Integrated Security=True" providerName="System.Data.SqlClient" />

</connectionStrings>


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

mat_carbon

I had exactly the same error when setting up a new database for logging. The problem was solved when I discovered the file permissions for both the mdf and ldf were incorrect. To ensure that ASP.NET can access these files from the App_Data folder you will need to set to Inherit from parent the permission entries that apply to child objects as seen in the Advanced file security settings.

And a couple of other things to be aware of..
1. If you attach the mdf file to an instance of SQLExpress in either Visual Studio or SQL Server Management Studio it will wipe out the Inherit from parent switch.
2. SQLExpress cannot be run in more than one process at a time. So your web application is still active and holds onto a connection (and this is what the Enterprise Library Logging Application Block does) then you'll not be able to open the mdf anywhere else. Of course the reverse is true also. It took me an age to spot this and its so easy to fall into the trap!


Top

Re: An attempt to attach an auto-named database ....\aspnetdb.mdf failed

mp5k

It seems that the only kind of connection allowed for an database stored in App_Data is USER_INSTANCE=TRUE. Once I moved the file to c:\myfolder\ , access could be as a server or a user instance.



Top