Hi,

Iam facing problems to connect to the new database after detach the aspnetdb.Simply the new database disappear (In SQL 2005 Management studio express the database contents disappear ! and I get an error when try to open it).If I try to connectto aspnetdb again I get an error telling me it is used by another process.I don't understand what is going on could any one explain to me?  

hi,

use this command in the sql query.... 

sp_detatch_db 'Database name'

thanks,

rajiv

Remember To mark as answer if it answered your question.

I have detach the aspnetdb file already and attach a batabase successfuly but the problem when I run the application I get the error:

The process cannot access the file '....\aspnetdb.mdf' because it is being used by another process.I set the connection string to my new database so what cause this error and how to fix it? 

Hi Buddy,

I think although you detached the database from your pc actually its not detached in the server.

So you have to come across some stored procedures

Please refer the following one www.msdn.com

Mark As Answer If this helps you

Further Queries Recommended

Happy Coding

 If you have aspnetdb attached in Management studio and if the webconfig is using attachdbfilename, its not going to work.

To get this to work, 

Either detach the aspnetdb from management studio before you run the application

or

Change the connection string to use database=aspnetdb

Thank you for your respond.The aspnetdb file doesn't appear in the management studio.How could I run the stored procedure you mentioned on the aspnetdb database file.The database is attached successfully to my new sql express server database with a new name.I can see it in visualstudio.but still when I try to run the application I get the error :

The process cannot access the file '...\ASPNETDB.MDF' because it is being used by another process.The connectionString seems to me set correctly.

When I try to exclude the aspnetdb file I get a similar error message to the one above.  

XPSCodes:

 If you have aspnetdb attached in Management studio and if the webconfig is using attachdbfilename, its not going to work.

To get this to work, 

Either detach the aspnetdb from management studio before you run the application

or

Change the connection string to use database=aspnetdb

As I read in a book I detached the aspnetdb file in the visualstudio.net solution explorer then in management studio express I attach the file with a new name.Then I modify the connection string to connect to the sqlexpress server database as  the following:

<remove name="LocalSqlServer"/>
  <add name="LocalSqlServer" connectionString="Data Source=MYCOMPUTER\SQLEXPRESS;Initial Catalog=NewDatabaseName;Integrated Security=True" />
  

I just observed that my connection string is for sql express instances(.dbo) not for an .mdf file so if I want the database file to still attached to the management studio(the second choice) what the connection string should be?.

Oh no.I have detached the database in management studio and set the connection string to use the aspnetdb.mdf file but the error still exist.

Hi TheEagle ,

Is your applicatoin(web site) still running? Note that sql express use UserInstance which means when your application is running, the database would be auto-attached to sqlexpress instance and when your application ends up, that database would be auto-detached from sqlexpress. So,even if you have elaborately detached that db from sql express, after you run your application again, and during your application runtime, that db(mdf file) is still attached. Based on my understanding, I think if you try to attach a databse to sqlexrpess which has already been attached, you would get the error message  that you are getting now.

Hope my suggestion helps

Bo Chen – MSFT:

Hi TheEagle ,

Is your applicatoin(web site) still running? Note that sql express use UserInstance which means when your application is running, the database would be auto-attached to sqlexpress instance and when your application ends up, that database would be auto-detached from sqlexpress. So,even if you have elaborately detached that db from sql express, after you run your application again, and during your application runtime, that db(mdf file) is still attached. Based on my understanding, I think if you try to attach a databse to sqlexrpess which has already been attached, you would get the error message  that you are getting now.

Hope my suggestion helps

Thank you for responding to me.I have detached that database in the Management studio express.A three options page appeared(keep,drop,..) I leave it as default which was keep then the database disappeared in Management studio express then I set the connection as the following:

<remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=D:\..\ASPNETDB.MDF;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>
</connectionStrings>

Then I run the application and the error prevent the application from strating.

Hope that you can help me as fast as possible.

TheEagle:

Thank you for responding to me.I have detached that database in the Management studio express.A three options page appeared(keep,drop,..) I leave it as default which was keep then the database disappeared in Management studio express then I set the connection as the following:

<remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=D:\..\ASPNETDB.MDF;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>
</connectionStrings>

So you still get that "datbase is used by another process" error. This indicates that aspnetdb.mdf is* still attached to sqlexpress*.  I think you can try to change you connection string to be:

<remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Data Source=.\SQLEXPRESS; Initial Catalog=&quot;ASP.NET DB&quot   ;Integrated Security=True; providerName="System.Data.SqlClient"/>
</connectionStrings>

Hope my suggestion helps

I remebered that I have another configuration file I created to publish the website so the connectionstring will be replaced.I make it an empty string to be sure it has no effect.I did as you told me and the application start but I get an exception:cannot open database aspnetdb requested by login the login failed.login failed for user MyComputer\ASPNET 

After making many things:refresh IIS,detach the Managementstudio database again with the option keep unselected,remove the connection to Managementstudio database in visualstudio.put the default connectionstring,disconnect the aspnetdb database.the application start successfully.But only when I close the database connection otherwise the error appear again.I need always to open the connection to modify the database then close it to pass this error which is not practical.if someone can at least guess what is going on please share us this thread.