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 ...Installing dnn431 error: Portal failed to installInstalling dnn431 error: Portal failed to install
Previous
 
Next
New Post
7/10/2006 3:12 AM
 
Val Lusis


Joined: 12/13/2005
Posts: 158

smehaffie wrote
Make sure the NetWorkServices Account (Win2003) or the ASP.Net account (Win2000) have List, Read, Execute, Write, and Modfy on the directory DNN is installed and all the files / sub-direcotries under the DNN directory.

Indeed... but for some reason when I gave the aspnet user permissions, it didn't apply them to subfolders and files, I had to force it to do that. Something has been changed on my computer and I wonder who's behind it... I have an idea - maybe it's Microsoft with one of the recent security updates, who knows... I didn't change anything that would prevent populating permissions correctly.

But for now, forcing permissions to child objects fixed the problem!

Waldis
 
New Post
7/10/2006 3:18 AM
 
Erik van Ballegoij


Erik van Ballegoij's Avatar

erikvanballegoij.com
Joined: 4/7/2004
Posts: 4445

windows folder security settings will only be propagated to child folders if childfolders are set up to "copy settings from parent".. AFAIK this behaviour is not influenced by MS security patches

cheers,

Erik

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn
 
New Post
7/14/2006 7:36 PM
 
dpathway

Joined: 7/13/2006
Posts: 12
ewe and Gluber -

did you manage to solve the original problem you were having? Grateful if you could post your solution, cos I think a lot of folks are having the same problem.

Thanks!
 
New Post
7/15/2006 2:39 PM
 
dpathway

Joined: 7/13/2006
Posts: 12

After struggling for 1.5 days trying to figure out what was causing that "Portal failed to install" error, I finally managed to fix it by doing the following (I was trying to install DNN 4.3.2 on W2k Pro):

  • Delete and recreate Database.mdb in the C:\InetPub\wwwroot\DotNetNuke folder (this is where I store my DotNetNuke files).
  • In Windows Explorer, edit the Properties of C:\InetPub\wwwroot\DotNetNuke (right click à Properties)
  • Under the Security tab, click Add and double click on ASPNET then click OK.
  • Select ASP.NET Machine Account, and grant Full control rights, the click OK.
  • Repeat the same for C:\InetPub\wwwroot, C:\InetPub and C:\ (I don't know if it is really necessary to do this for all the folders or to grant Full control rights, but it did the trick for me).

Reinstall DNN by opening your browser and pointing to http://localhost/DotNetNuke (this assumes you have created a website alias "DotNetNuke" from C:\InetPub\wwwroot\DotNetNuke in IIS).

I understand the steps above are very elementary for experienced DNN administrators, but for newbies like me, I really needed instructions like this to fix this problem.
 
New Post
7/15/2006 3:00 PM
 
Shawn Mehaffie

Joined: 1/4/2003
Posts: 2313
You should not have to give ASP.Net user full control on the DNN directory and all the sub-direcotries.  I would give the ASP.Net (Win2000) or NetworkServices (Win2003) user the following permissions.

List
Read
Execute
Write
Change

The only other access you are granting the user by giving it full is to change directory permissions.  This make you site less secure and if it was hacked a hacker could change your directory permissions. 
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing dnn431 error: Portal failed to installInstalling dnn431 error: Portal failed to install


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