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 ...Workaround/Fix to DotNetNuke_template.mdf messageWorkaround/Fix to DotNetNuke_template.mdf message
Previous
 
Next
New Post
5/3/2006 4:23 PM
 

Here is a fix/workaround to the infamous message:

Could not find file '...\Website\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'

By default, the "Connection String for SQL Server 2000/2005" is commented out, leaving the "Connection String for SQL Server 2005 Express" as the connection string used during site creation.

I don't know the cause, probably permissions not granted to a "default SQL user or group".

But because the Connection String for SQL Server 2000/2005 is a valid form for SQL Server 2005 Express.

This the solution I came up with:

Step 1

Start with a fresh web.config, copied from release.config

Under
  <connectionStrings>

Comment out the connection String for SQL Server 2005 Express thus :


<!-- Connection String for SQL Server 2005 Express
    <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />
  -->   
and uncomment the Connection String for SQL Server 2000/2005 thus :

    <!-- Connection String for SQL Server 2000/2005     -->
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />
     
Repeat steps under
<appSettings>
thus:
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules  
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
   
-->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules    -->
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>

Step 2

If you have followed the steps to create an empty database
and create a user with dbo role on that database then
    fill in:
    Server=NameOfYourServer;
    Database=NameOfCreatedDatabase;
    uid=NameOfUserWith_dboRole;
    pwd=PasswordOfNameOfUserWith_dboRole;
   
    under both <connectionStrings> and <appSettings>

Step 3   
     Save web.config
     If your IIS server was running, stop and start

PS

I am curious to know what configuration has to be done for the Connection String for SQL Server 2005 Express to work.

    

 
New Post
5/3/2006 6:37 PM
 
thanks!

opened web.config in notepad several times before I noticed the connection string settings commented out.

regards - John
 
New Post
5/9/2006 7:06 AM
 

THIS IS A REAL HOT FIX... Many Many Thanks Milliwatt

I've been trying to install DNN for about a week now, and after running into many many problems the DoyNetNuke_template error message was the last one on the list...

I can now finally play with DNN! At last!!!!!!!

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Workaround/Fix to DotNetNuke_template.mdf messageWorkaround/Fix to DotNetNuke_template.mdf message


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