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
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...5.6.0 to 5.6.1 failure...5.6.0 to 5.6.1 failure...
Previous
 
Next
New Post
3/14/2011 5:54 PM
 
Lou Syracuse


Joined: 10/16/2007
Posts: 29
Thank you for your ideas and links! I tried the above links with no change.

Everything (IIS, SQL,Webcode,.. ) is one a single 2008 R2 64-bit box. No VM's or UNC's. Nothing else on the box.... it's as plain as can be.

I also relocated the site a directory under c:\websites rather than under wwwroot and created a new entry in IIS.... Same result. I even gave full rights to 'everyyone', but still got the same error.

I KNOW the update works on my site, I created a 2008 R2 64 VM on my notebook and copied the site/database to it and it ran perfectly there. It has to be something on the server.. but what?
 
New Post
3/14/2011 7:21 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
At the start of this thread you indicated that you granted full file system permissions to several user accounts including Network Service and IIS AppPool. Since your server is running IIS 7.5, the default AppPool is not Network Service as it would have been on IIS 6 and 7. Perhaps your account IIS AppPool is the correct default account for the IIS Identity account (ASP.Net worker process account) but when setting permisions on the root install folder, the default IIS Identity pseudo account has to be ented in the Windows Security --> Edit --> Add Group or User names dialog as "IIS AppPool\DefaultAppPool" and once added will show up in the list of users as "DefaultAppPool". Please try granting full file system permissions including modify to the "IIS AppPool\DefaultAppPool" pseudo-user account on the root website install folder and make sure that all child folders inherit that permission.

You may also want to double check what IIS Identity account has been assigned to the Application Pool that is associated with the site's IIS application. The default would be "ApplicationPoolIdentity" which relates to the pseudo account "IIS AppPool\DefaultAppPool" to which full permissions must be granted when setting the root folder's permissions in the above.
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
3/15/2011 11:10 AM
 
Lou Syracuse


Joined: 10/16/2007
Posts: 29
William,

Thank you for your very detailed reponse.  I have a much better understanding of how IIS and App Pools work now.

I made the changes you listed... The application Pool's identity was set to ApplicationPoolIdentity, and the pseudo account "IIS AppPool\DefaultAppPool" was NOT granted rights to the root folder.     I added those rights, but the update still failed.

So....   given the knowledge you gave me I took a chance and changed the Application Pool identity to Network Service and restarted IIS... and the update complted normally!

I'm not sure why it wouldn't work  after I granted the rights to IIS AppPool/DefaultAppPool, but at this point I'm not going to spend many cycles trying to figure it out.  The site is updated, and I can switch it back to ApplicationPoolIdentity if need be and the site still runs just fine.     We're moving the site into production next month, and when the a new server comes in I'll have more time to play around with it.  Thanks to you now I have a much better understanding of how to set it up.

Thanks again for your help, I never would have figured this out on my own!  :)
Lou
 
 Page 2 of 2
Previous12 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...5.6.0 to 5.6.1 failure...5.6.0 to 5.6.1 failure...


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