Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...install error install error 'couldn't find file DotNetNuke_template.mdf'
Previous
 
Next
New Post
4/25/2006 11:52 AM
 
Bill Wallace

Joined: 4/17/2006
Posts: 29
I had the same problem ... I just deleted that database file from the directory and it just came back to life. Don't ask me why .. it just worked for me.
 
New Post
4/26/2006 2:06 AM
 
Eric Henson

mehenson.com
Joined: 9/11/2004
Posts: 113

fireant wrote
I had the same problem ... I just deleted that database file from the directory and it just came back to life. Don't ask me why .. it just worked for me.

What database did you delete?  I have this problem and would really appreciate knowing what you did to get it working.

Thanks,
 
New Post
4/27/2006 7:31 AM
 
Bill Wallace

Joined: 4/17/2006
Posts: 29
I found the file here http://www.johnczimmerman.com/Default.aspx?tabid=288 I installed it into SQLexpress .. then deleted it .. and poof .. it all started to work.
 
New Post
5/4/2006 7:41 PM
 
Eddie Parker

Joined: 4/20/2006
Posts: 1

I think the problem has something to do with Mixed Mode Authentication being selected when SQLExpress is installed.  I changed the Web.Config connection string from

     connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"

to use SQL Authentication with

     connectionString="Data Source=.\SQLExpress;uid=sa;pwd=himom;AttachDBFilename=|DataDirectory|Database.mdf;"

and all of my installation problems disappeared.
 
New Post
5/4/2006 10:13 PM
 
Eric Henson

mehenson.com
Joined: 9/11/2004
Posts: 113

rfiriri1,

I think that I see what caused your problem.  By looking at your web.config script, it looks like you are using the settings for SQL2005 Express instead of SQL 2000.  To use SQL 2000, you have to rem out or delete the SQL Express info and remove the rem for the SQL 2000/2005 part.

Here is an example of a working connection string for SQL 2000.  Make sure to note where the <!--  and --> are because these rem out text.  Whatever between those rem's will not be recognized as valid script.

  <connectionStrings>
    <!-- Connection String for SQL Server 2000/2005   -->
    <add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid=dnnuser;pwd=password;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules    -->
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=dnnuser;pwd=password;" />
    <add key="InstallTemplate" value="DotNetNuke.install.config" />

Good Luck and let us know if this doesn't work.
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...install error install error 'couldn't find file DotNetNuke_template.mdf'


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