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...Having upgraded my DNN site, I now get an error instead of the upgrade wizardHaving upgraded my DNN site, I now get an error instead of the upgrade wizard
Previous
 
Next
New Post
5/7/2010 3:54 PM
 
Hi

Having followed the instructions in this article (Blogs - Upgrading DotNetNuke), I was a little surprised to find that I now get an error page instead of the upgrade wizard. I searched for the instructions because I have tried to upgrade a site before without instructions, & when it didn't work I just restored the site from a backup I took just before the attempt.

Just to clarify, I followed these steps:
  1. I downloaded the upgrade package for version 5.04.01
  2. I unzipped its contents into the web site folder on the server
  3. I renamed web.config to something else, renamed release.config to web.config, & copied the two SQL connection related settings & the machinekey setting from the old web.config into the new one, replacing the default settings in that file
  4. I then opened up the home page from the server, & was presented with the following:

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>



Did I do something wrong, or missed something?

Thanks.
 
New Post
5/7/2010 3:58 PM
 
Can you either login to the webserver and pull the page up to see what the actual error is, or turn off custom errors and load the site?  The runtime error page your have copied won't help debug the issue because it doesnt show what the real error is

Nick Christy Director of Technology, r2Integrated
 
New Post
5/8/2010 6:04 AM
 

D'oh, sorry! The first time I posted it, I copied the error message from the server, but for some reason, the posting didn't take & I had to resubmit it. Slightly frustrated & rushing, I just noticed I must have copied this useless error from my laptop's browser, rather than the server.

Here is the error displayed locally on the server:

Server Error in '/' Application.

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. 

Compiler Error Message: BC30002: Type 'Web.HttpResponse' is not defined.

Source Error:

Line 32: Implements System.Web.IHttpHandler Line 33: Line 34: Private Sub RenderToResponseStream(ByVal Response As Web.HttpResponse, ByVal controller As XmlController) Line 35: ' save script timeout Line 36: Dim scriptTimeOut As Integer = HttpContext.Current.Server.ScriptTimeout

Source File: C:\Inetpub\wwwroot\EastbourneIT\App_Code\XML\Handlers\download.vb    Line: 34 







Version Information: Microsoft .NET Framework Version:2.0.50727.3607; ASP.NET Version:2.0.50727.3082

 
New Post
5/8/2010 7:57 AM
 
That is a known error in the XML module caused by a namespace conflict introduced in DotNetNuke 5.3.0. Remove all files from the site folder App_Code\XML. That should then allow your site to come back up. Then, log in as host user, navigate to Host-->Extensions. Scroll to the bottom of the page and click on Install Available Extensions. Select the (updated) XML module then click "Install Available Extensions".

If you have the DotNetNuke Chat module installed, you will get a similar error. Currently there is no updated version of the chat module available. You will need to make a couple of simple changes to one of the files in the App_Code\Chat folder. Details should be in the Chat module forum.

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
5/8/2010 8:21 AM
 
Excellent, thanks. I think I had all extensions installed, as I am trying DNN out on a couple of sites. I will follow your suggestion & report back...

Thanks for the quick response!
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Having upgraded my DNN site, I now get an error instead of the upgrade wizardHaving upgraded my DNN site, I now get an error instead of the upgrade wizard


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