Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQLExpress mdf being used by another processSQLExpress mdf being used by another process
Previous
 
Next
New Post
2/2/2006 4:57 PM
 

I have an installtion of 4.0.2 working under sql2000 on one machine. I backed up the database.

I installed 4.0.2 on another machine. On this machine I have SQLExpress. I've set up config to point to SQLExpress.

I created the mdf in c:\dnn402\website\app_data.

I then restored my SQL2000 db into the new DNN402.mdf.

When I attempt to start DNN I get ...

Error Installing DotNetNuke

Current Assembly Version: 04.00.02

ERROR: Could not connect to database specified in connectionString for SqlDataProviderSystem.Data.SqlClient.SqlException: Unable to open the physical file "C:\DNN402\WebSite\App_Data\DNN402.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".

 

The appropriate web.config settings are ...

<connectionStrings>

<!-- Connection String for SQL Server 2005 Express -->

<add name="DotNetNuke" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|DNN402.mdf;" providerName="System.Data.SqlClient" />

<!-- Connection String for SQL Server 2000/2005

<add name="DotNetNuke" connectionString="Server=(local);Database=DNN402;uid=DotNetPortalUser;pwd=dnpu;" providerName="System.Data.SqlClient" />

-->

</connectionStrings>

<appSettings>

<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->

<add key="DotNetNuke" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|DNN402.mdf;" />

<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules

<add key="DotNetNuke" value="Server=(local);Database=DNN402;uid=DotNetPortalUser;pwd=dnpu;" />

-->

 

Thanks

 
New Post
2/6/2006 3:56 PM
 

That is a caveat of MSSQL Express 2005; when you attach to the file (directly) the file is then locked.

SQL Server (not express) doesn't have this limitation.

I do not think the express version will allow multiple connections to the same file; so I have heard.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQLExpress mdf being used by another processSQLExpress mdf being used by another process


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out