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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Error Upgrading Community versions 5.2.2 to 5.2.3...Error Upgrading Community versions 5.2.2 to 5.2.3...
Previous
 
Next
New Post
3/3/2010 6:15 PM
 

Roger, I'm jumping in late into this thread, but have you tried resetting the permissions on the website's root folder to make sure that all the child permissions are propagated properly?

Also, Since you are on R2, can you check the Application Pool in IIS to make sure that the account that the website is running under is actually the Network Service account that you have permissions setup for (see previous step) and not some other account?


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
3/3/2010 6:33 PM
 

Chris,

Actually with R2 (IIS 7.5) the App Pools should not be running under Network Service, rather they should be running as IIS AppPoolIdentity.  I commented on that in this thread. You can also read more about the change here.

HTH



 
New Post
3/4/2010 5:39 AM
 

I appreciate all the help I can get with this one.

I can confirm that I have re-applied the security to the entire folder structure of the sites in question and confirmed right down to individual files that the settings have been passed through.

I have checked in IIS (7.5) that the Applications are all running as ApplicationPoolIdentity

Do you think it's worth trying removing the server from the domain and running it as a stand-alone server??

I am really baffled by what's going on.

I have an additional problem that has occurred sometime during one of my backup/restore operations.
The site that I have been testing this on has lost it's Forum module and I can't seem to get it back.
(I mentioned it earlier in one of my postings)

Cheers

Roger (already lost most of my hair but pulling out the rest now)

 
New Post
3/4/2010 6:51 AM
 

Thanks for the help Chris.

The article at http://learn.iis.net/page.aspx/624/ap... helped me to resolve the problem.

I am happy to report that all 4 sites are now up and running with version 5.2.3

I did appear to have a problem with two of the sites, they both came up with the following error.

Upgrading DotNetNuke

Current Assembly Version: 05.02.03

Current Database Version: 05.02.02

 

Upgrade Status Report

00:00:00.023 - Upgrading to Version: 05.02.03
00:00:00.272 -   Executing Script: 05.02.03.SqlDataProvider 
Success
00:00:03.288 -   Executing Application Upgrades: 05.02.03 
Success
00:00:03.291 -   Cleaning Up Files: 05.02.03 
Success
00:00:03.296 -   Updating Config Files: 05.02.03 
Success
00:00:03.299 - Performing General Upgrades

 


Server Error in '/' Application.

 

I did appear to have a problem here but, as I was just about to restore the files, I refreshed the page and up came the site.

I then logged in and went to have a look at the version and it reported, to my surprise, 5.2.3

 

The important thing that I found was setting the "permissions" on the site.

Adding the "DefaultApp" user seemed impossible at first, because it didn't exist when I searched for it.

However when adding the user I realised that it is important to select the local machine name from the "Locations" button and then copy in

  "IIS AppPool\DefaultAppPool"  (without the quotes)  This then added the "DefaultApp" user to the list and I was able to give full rights to the user.

 

I hope this helps someone else.

 

Should I add my other query, regarding the disappearing Forums Module, in a different forum?

 

Regards

 

Roger

 
New Post
3/4/2010 8:10 AM
 
Hi! hi have the same error 5.2.2 upgrade to 5.2.3 Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. I try in my local pc befor to port on the production server and doesen't work. Before the copy of the file the 5.2.2 version work well!!!!! No permission problem No webconfig problem Rmartin
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Error Upgrading Community versions 5.2.2 to 5.2.3...Error Upgrading Community versions 5.2.2 to 5.2.3...


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