Post install issue - Installing DNN Platform

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

Home All Forums

1/1/2006 3:34 PM

Christopher Bosak

Joined: 6/26/2005

Posts: 2

Post install issue

After installing DNN 4.0.2, it's able to run on the ASP.NET Dev server, but, if I try to access it normally, I get this error.

ERROR: Could not connect to database.

Unable to open the physical file "C:\DotNetNuke Website1\App_Data\Database.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)". An attempt to attach an auto-named database for file C:\DotNetNuke Website1\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Can anyone help?

- Chris

1/4/2006 10:55 AM

Charles Nurse

Joined: 2/9/2004

Posts: 3652

Re: Post install issue

ViperBorg wrote

After installing DNN 4.0.2, it's able to run on the ASP.NET Dev server, but, if I try to access it normally, I get this error.

Not sure what you mean by "normally"?

ViperBorg wrote

Unable to open the physical file "C:\DotNetNuke Website1\App_Data\Database.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)". An attempt to attach an auto-named database for file C:\DotNetNuke Website1\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

The default connection string used in DotNetNuke, uses the new capability of SQL Server 2005, to attach to a Database file and create an Auto-named instance. I have found that occasionally you get the above error, because SQLServer 2005 thinks you already have a Database attached with the name it is trying to use.

One solution is to add the Initial Catalog=xxxxx; to the Connection String where xxxxx is a name of your choosing.

Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here

MVP (ASP.NET) and
ASPInsiders Member

5/27/2006 8:36 AM

Mark Fruhauf

Joined: 5/15/2006

Posts: 1

Re: Post install issue

I get the same error ... I have inserted the initial string but still get errors,

ERROR: Could not connect to database specified in connectionString for SqlDataProviderSystem.Data.SqlClient.SqlException: Unable to open the physical file "D:\Websites\Frucom.co.za\App_Data\frucom.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)". Could not attach file 'D:\Websites\Frucom.co.za\App_Data\frucom.mdf' as database 'frucom'.

HELP !!

6/1/2006 7:43 AM

Michael Flanakin

michaelflanakin.com
Joined: 4/5/2004

Posts: 994

Re: Post install issue

Can you manually login to the DB with the credentials specified in the web.config file?

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

11/12/2007 9:36 AM

rainley

Joined: 11/12/2007

Posts: 1

Re: Post install issue

I got this error because Dev Studio decided to open the database file from the solution in the server explorer. This meant the install wizard couldn't access it. I removed the connection from the server explorer and the connection worked.

Page 1 of 2

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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)