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 ...4.x and 1and1 -- installed but not working4.x and 1and1 -- installed but not working
Previous
 
Next
New Post
6/13/2006 1:53 AM
 

I am facing problem while insatlling DotnetNuke

The error message is like that:-

Could not find file 'D:\dotnetnuke\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:\dotnetnuke\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[FileNotFoundException: Could not find file 'D:\dotnetnuke\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'.]
   System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +2014237
   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

I dont know why This problem is coming can anyone please help me to find it.
 
New Post
6/14/2006 9:00 AM
 
Here is the official response from 1and1 regarding this problem. I got this after a lengthy exchange of emails, most of which where written by staff who obviously had no clue about my problem.

"Unfortunately we do not provide scripting support.  If you would like
the ASP.NET framework downgraded to version 1.1, please let us know."

So to clarify, if you want to run DNN4 on 1and1 you can not. You have to run DNN3 and ask them to downgrade your package to .NET 1.1.

If you are thinking of using 1and1 for hosting DNN then my recomendation is dont'! I am concidering switching providers myself.
 
New Post
6/19/2006 6:10 PM
 

That sucks **moderator edit - profanity understood, but removed :) **. Fortunately, my largest DNN website (ie the one that would take me the longest to rebuild from scratch) is still running 3.2.2 so I'll contact 1and 1 to downgrade that site to .Net 1.1.

The other sites have already been upgraded to 4.0, so Im going to have to try and downgrade that, but Im already thinking it's going to be a "do-over" and prepare to move to a new host when the year is up.

I'm still going to try what that earlier post recommended and change the defaultmaxsize to 4096, just to see if it works, before trying to downgrade.

 

 
New Post
6/21/2006 1:52 PM
 
Since we've come to the conclusion that 1and1 now sucks (no profanity this time ;) ) Im looking at cancelling the hosting with them and moving to somewhere else, someone who DOES support not just ASP.Net and scripting, but specifically DNN.

Any suggestions?

 
New Post
6/21/2006 4:10 PM
 
Although I still have an account with 1&1 and host webs there I have recently opened an account with WebHost4Life to try them out. WH4L on paper look like the same price as 1&1 but there are plenty of hidden costs that they don't tell you about until you try and add features that come included in the 1&1 price. For example, "unlimited domain pointing" in WH4L parlance means 2 domains and you pay $15/year for each extra after that. 1&1 really is unlimited. On WH4L you also have to pay extra for each email domain that you want to use ($10/year I think) which is included on the 1&1 packages.

However, if you can live with the concept of not knowing what extras you have to pay for then try WH4L as you can run ASP.NET 1.1 and 2.0 side-by-side.

I recently had to ask 1&1 to downgrade me from ASP.NET 2.0 to 1.1 because it broke a bunch of stuff I had and 1&1 don't offer side-by-side 1.1 and 2.0 like WH4L.

I too am interested in installing DNN on 1&1 but I don't want to have to install 3.x and then go through an upgrade process later. I want to go straight for 4.x (currently 4.3) on ASP.NET 2.0 so I will keep an eye on this thread and wait until some solutions are found.

I am thinking that 1&1 would do well letting their 2nd tier MS customers have 2 accounts in their package. 1 with ASP.NET 1.1 and another with 2.0 which would probably solve a lot of people's problems...

ver 4.3.1 (to 8 July 2006) ver 4.3.2 (to 20 July 2006) ver 4.3.3 (to 5 Aug 2006) ver 4.3.4 (to 20 Sep 2006) ver 4.3.5 (to 25 Dec 2006) ver 4.4.0 (to date)
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...4.x and 1and1 -- installed but not working4.x and 1and1 -- installed but not working


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