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 ...Could not find file .....SqlDataProvider\DotNetNuke_template.mdfCould not find file .....SqlDataProvider\DotNetNuke_template.mdf
Previous
 
Next
New Post
1/15/2006 4:10 PM
 
Pierre Marklund

www.xact.nu
Joined: 7/18/2005
Posts: 2

Hi!

I have a brand new W2K3 Server with IIS6 and .Net 2

After unzipping the Install-package for DNN 4 and folowing the install-doc I get this error:

Could not find file 'E:\Inetpub\DNN4\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not find file 'D:\Inetpub\DNN4\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'.


It seams like the install-scripts is trying to copy a file that does not exist

 

[FileNotFoundException: Could not find file 'D:\Inetpub\DNN4\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'.]
   System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +2014125
   System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) +488
   DotNetNuke.Data.SqlDataProvider.GetProviderPath() +220
   DotNetNuke.Common.Globals.GetUpgradeStatus() +335
   DotNetNuke.Common.Global.CheckVersion() +187
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +316

And I also found an extra row in my web.config that's not in the install-doc:

    <data
      defaultProvider="SqlDataProvider">
      <providers>
        <clear/>
        <add
          name="SqlDataProvider"
          type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
          connectionStringName="SiteSqlServer"
          upgradeConnectionString=""
          providerPath="~\Providers\DataProviders\SqlDataProvider\"
          objectQualifier="dnn_"
          templateFile="DotNetNuke_template.mdf"
          databaseOwner="dbo"/>
      </providers>
    </data>

It seams coneccted to the problem.

What to do?

I do not want to install the VSexpress on this production server.

Best regards

Pierre Marklund
 
New Post
1/16/2006 2:41 PM
 
jared Arnold

Joined: 6/15/2005
Posts: 1
I installed vsexpress on a workstation to build the application then uploaded to a server at which point I struggled with this error myself. As far as I can tell there is no dotnetnuke_template.mdf even in a working install. From your path above it looks like you are installing dnn at the root or above the root of your web server. I tried for 2 days to get this to work and was unsuccessful so I just walked away from it for a couple of days. I came back to it today and tried to install in a folder underneath the default folder c:\inetpub\wwwroot\dotnetnuke and left the home directory of the server set to c:\inetpub\wwwroot\

After doing that everything worked. I hope that helps you. Good luck.  Hopefully you have a workstation to build on.
 
New Post
1/16/2006 6:23 PM
 
Paul Trusty

Joined: 1/15/2006
Posts: 1

I was experiencing the same problem.

Upon close examination of the web.config file, I found that I had filled in the connection string for SQL 2000/2005, and left it commented out. The "default" is the SQL express is not commented out, but the SQL 2000/2005 is commented out ( <!--     --> ) 

After I corrected the connection strings, I ran it and it worked.

Regards

Paul
 
New Post
1/17/2006 4:53 AM
 
Pierre Marklund

www.xact.nu
Joined: 7/18/2005
Posts: 2

Thx guys!

I now have found what the problem was.

I followed the install doc from the doc-zip written by Charles Nurse.

In it it describes how to create a new db with SQL Express but I did not find any reference to that it should be created in APP_DATA, so I just went on creating one with my own name at the SQL default location.

It then describes how to alter the web.config connection strings and of course you imagine the you should use the SQL express setting if using Express ?!

But that is when you run in to trouble!! Some mekanism is then asuming that your database should be located at APP_DATA and it also looks for it with the name of "dbname_template.mdf".

My solution to the problem is to mark out the SQL express connection settings and using the normal SQL 2005 settings.

To remember is that you probably have to enable Named Pipes in your Express settings for how your db could be accessed.

My connection strings now looks like this:

"Server=SERVER\SQLEXPRESS;Database=DbName;uid=dbusr;pwd=guesswhat;"

BTW:

I still dont know if I will run in to trouble because i am not using an virtual directory.

 

Best regards

Pierre
 
New Post
1/17/2006 12:19 PM
 
Charles Nurse


Charles Nurse's Avatar

Charles Nurse's Avatar

Joined: 2/9/2004
Posts: 3652
In the default connection String for SQL Express

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

the AttachDBFilename=|DataDirectory|Database.mdf; setting is what indicates that the Database file should be in App_Data (ie the |DataDirectory| part.


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
View my profile on LinkedIn
 
 Page 1 of 3
123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Could not find file .....SqlDataProvider\DotNetNuke_template.mdfCould not find file .....SqlDataProvider\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