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 ...1and1 DotNetNuke 4.3.51and1 DotNetNuke 4.3.5
Previous
 
Next
New Post
12/25/2006 1:13 AM
 
Peter Fattore


Joined: 8/31/2005
Posts: 15

Version 4.4 was just released. Check out the results of the install script! So little :-) yay

Installing DotNetNuke

Version: 04.04.00



Installation Status Report

00:00:00.171 - Installing Version: 4.4.0
00:00:00.171 - Installing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.265 - Installing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:11.672 - Installing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:17.140 - Installing MemberRole Provider:
00:00:17.140 -   Installing Script: InstallCommon.sql
00:00:17.750 -   Installing Script: InstallMembership.sql
00:00:18.625 -   Installing Script: InstallProfile.sql
00:00:18.828 -   Installing Script: InstallRoles.sql
00:00:19.531 - Performing General Upgrades
00:00:20.016 - Loading Host Settings:
00:00:20.203 - Configuring SuperUser:
00:00:20.844 - Installing Modules:
00:00:20.953 -   Installing Module File HTML_03.03.00_Install:  Success
00:00:22.266 -   Installing Module File Links_03.03.00_Install:  Success
00:00:24.328 - Executing Additional Scripts:
00:00:24.328 -   Creating Portal: My Website
00:00:30.984 -   Successfully Installed Portal 0:
00:00:30.984 - Installing Optional Resources:
 
New Post
12/25/2006 11:52 AM
 
Peter Fattore


Joined: 8/31/2005
Posts: 15

I got everything working 100% now! (as far as I can tell so far). I found some very quick and easy steps to make the install painless

Steps to install DotNetNuke 4.4.0  on 1and1 MS Hosting

1. [web files] Upload DNN install to /tmp directory
2. [web files] Unpack to root and rename to /dnn
3. [web files] Set /dnn settings to give full permissions to all users (probably should tighten up to only allow what we need)
4. [web files] Add /dnn to applications
5. Modify web.config for your SQL server settings (two different places). Also change the dbo entry to your db username (databaseOwner="dbox")
6. [web files] Upload web.config to /dnn
7. Launch site.com/dnn to install everything. DO NOT ENTER SITE
8. Launch SQL admin and go to query analyser.
9. Enter "select * from portalalias" and hit submit. HTTPAlias should say site.com/dnn
10. Enter the following 3 lines, then hit submit. Notice the no trailing slash.
update PortalAlias
set HTTPAlias = 'www.site.com'
where PortalAliasID = 1
11. Do step 10 again to verify the HTTPalias is now www.site.com
12. Go to your FTP client, move the contents of /dnn to the root of your site. (all permissions that were set in webfiles will stay with the files) THIS IS A BIG TIME SAVER!
13. Go to the root of your website and enjoy! You should not have to copy the siteurls.config (I don't think I did, because when I tried to copy it prematurely, it was already there!)
 
New Post
1/4/2007 4:58 PM
 
Bann

Joined: 1/2/2007
Posts: 4
Hi,

I configured my 1and1 Webspace as told before. After some tries i get finally a visible and stable version but,...

all my modules seen to be misconfigured. I see all the standard modulcontainers such as "links", "Welcome to DotNetNuke",... but all of them display the following error:

Error: Links is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The file '/DesktopModules/Links/Links.ascx' does not exist. ---> System.Web.HttpException: The file '/DesktopModules/Links/Links.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

Any idea where to find the error?

greetings and thx


Bann
 
New Post
1/4/2007 10:38 PM
 
Frank Corrao

www.raiseepilepsy.org
Joined: 4/7/2005
Posts: 122

peterfnet,

Way to go.  I installed 4.4 on the day after christmas and didn't have any trouble except some of the modules didn't get installed properly so I re-installed the modules and it worked like a charm..

Version: DNN 4.4.1
Hosting Provider: 1and1
RAISE
 
New Post
1/4/2007 11:29 PM
 
Peter Fattore


Joined: 8/31/2005
Posts: 15

I had the same problem too. You just need to move the features.config file first to the DNN ROOT and I think it will fix the problem with the modules not installing. I would go to module definitions and it would get pissed off (after install). I think I moved features.config to the root and everyting fell into place
 I told it to install all the modules it found and good things happened. Note step 2.5 :-D

Just made a few small fixes and reposted the full steps. 

Steps to install DotNetNuke 4.4.0  on 1and1 MS Hosting

1. [web files] Upload DNN install to /tmp directory
2. [web files] Unpack to root and rename to /dnn
2.5 [web files] Copy /dnn/config/features.config to /dnn  (TEST after install to make sure modules install, post your results)
3. [web files] Set /dnn settings to give full permissions to all users (probably should tighten up to only allow what we need)
4. [web files] Add /dnn to applications
5. Modify web.config for your SQL server settings (two different places). Also change the dbo entry to your db username (databaseOwner="dboxxxxxxx")
6. [web files] Upload web.config to /dnn
7. Launch site.com/dnn to install everything. DO NOT ENTER SITE
8. Launch SQL admin and go to query analyser.
9. Enter "select * from portalalias" and hit submit. HTTPAlias should say site.com/dnn
10. Enter the following 3 lines, then hit submit. Notice the no trailing slash.
update PortalAlias
set HTTPAlias = 'www.site.com'
where PortalAliasID = 1
11. Do step 9 again to verify the HTTPalias is now www.site.com
12. Go to your FTP client, move the contents of /dnn to the root of your site. (all permissions that were set in webfiles will stay with the files) THIS IS A BIG TIME SAVER!
13. Go to the root of your website and enjoy! You should not have to copy the siteurls.config (I don't think I did, because when I tried to copy it prematurely, it was already there!)
 
 Page 12 of 19
Previous123...111213...19Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...1and1 DotNetNuke 4.3.51and1 DotNetNuke 4.3.5


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