Error with ASPNETDB.mdf once deployed the application web

[CFTK]

This is the error I get when I try to login in my application from
another machine:

An attempt to attach an auto-named database for file C:\Documents and
Settings\....\A pp_Data\aspnetd b.mdf failed. A database with the same
name exists, or specified file cannot be opened, or it is located on
UNC share.

What should I do..? I´m lost..!

thanks!

[mike]

This is what I did on WebHost4Life to get mine up and running

upload the ASPNETDB.MDF file to the App_Data folder - do not upload the
LDF file.

Here is the connection string entry in my web.config that is working.

<connectionStri ngs>
<remove name="LocalSqlS erver"/>
<add name="LocalSqlS erver" connectionStrin g="Data
Source=.\SQLEXP RESS;
AttachDbFilenam e=|DataDirector y|\ASPNETDB.MDF ;
Integrated Security=SSPI;

Connect Timeout=30;
Initial Catalog=ASPNETD B;"
providerName="S ystem.Data.SqlC lient" />
</connectionStrin gs>

NOTE: The blank line was User Instance=True; That caused problems and
I read some other posts saying that it should be removed.

Hope this helps! I have seen alot of folks having trouble deploying
their SQLExpress DB's It would be nice if there was an easy way to
deploy and not mess with settings in config.


CFTK wrote:

This is the error I get when I try to login in my application from
another machine:

An attempt to attach an auto-named database for file C:\Documents and
Settings\....\A pp_Data\aspnetd b.mdf failed. A database with the same
name exists, or specified file cannot be opened, or it is located on
UNC share.

What should I do..? I´m lost..!

thanks!