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 ...Upgrade to 3.2.x failsUpgrade to 3.2.x fails
Previous
 
Next
New Post
1/9/2006 12:57 PM
 

Hi,

I've tried to upgrade my production DNN environment (running v3.0.12) both to 3.2.1 and 3.2.2.  In both cases, the process fails.  Or at least, the upgrade appears to work, but when I then attempt to access the one live portal running in this environment, I just get a blank page with 'An Error Has Occurred', plus red triangle, twice at the top of the page.  No other errors or clues I'm afraid!

In both cases, I used the supplied release.config as my new web.config, with the SiteSQLServer entry updated - machine keys were as normal.  I couldn't see anyhting else different between my old web.config and the new one, though it's not all that easy to compare them!

Anyone got any ideas what this could be?

Thanks,

Michael 

 
New Post
1/9/2006 1:48 PM
 
mikew5163 wrote

 - machine keys were as normal. 



What do you mean by machine keys were as normal?

Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
1/9/2006 2:23 PM
 

I mean the Machine validationKey and the MachineDecryptionKey were the same as those found in a 'fresh' release.config.  As per your Installation Guide (1.0.03, page 23), these look like the only thing, other than the SiteSQLServer entry, that I might need to change when making a new web.config from the new version's release.config.  I just mentioned them to rule them out as a potential problem.

I did try doing things the other way round too - i.e. I took my old (working) web.config, and just added the missing sections you mention on page 24 (navigation, caching and dblogging provider sections).  That gave me an asp.net error pointing to the first of the sections I inserted, so I guess I didn't insert them in the right place or in the right way. 

Thanks for your reply - if you can offer any further advice or suggestions, that would be really helpful.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade to 3.2.x failsUpgrade to 3.2.x fails


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