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 from 3.2 to 3.3 failsUpgrade from 3.2 to 3.3 fails
Previous
 
Next
New Post
6/13/2006 10:25 PM
 
After upgrading from 3.2 to 3.3 home page doesn't display any content and can't login. No error page is displayed. Just doesn't go anywhere. Thank god it was only a test site. Are there log files to look at or upload? Used install doc's from 3.2 since there were none with 3.3. Thanks!
 
New Post
6/14/2006 4:39 AM
 
I have not encountered this behaviour during upgrades - do you use any specific 3rd party modules or compression?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/14/2006 11:55 AM
 
Remember to copy the connection string and encryption keys when upgrading.

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
6/14/2006 12:50 PM
 

Copied the keys and install date from the old web.config file. No special modules or compression.

I also tried to do a clean install and it errors saying I haven't created the application in IIS even though I did.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:

Line 68: 		<customErrors mode="RemoteOnly" />
Line 69: 		<!-- Forms or Windows authentication -->
Line 70: 		<authentication mode="Forms">
Line 71: 			<forms name=".DOTNETNUKE" protection="All" timeout="60" />
Line 72: 		</authentication>

Source File: c:\inetpub\wwwroot\dunfamily\web.config    Line: 70


Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

 
New Post
6/14/2006 12:54 PM
 
Ok, never mind regarding the clean install. I had to go into IIS and manually create the application from the default website folder as creating a new website didn't do this.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade from 3.2 to 3.3 failsUpgrade from 3.2 to 3.3 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