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 05.02.00 to 05.02.01 failedupgrade from 05.02.00 to 05.02.01 failed
Previous
 
Next
New Post
1/17/2010 4:22 PM
 

I tried to upgrade my site from 05.02.00 to 05.02.01 earlier. I know my host has everything needed to run it, and previous upgrades for prior versions have worked with no problems.

However, after uploading all the files in the upgrade zip, when trying to access either the index page, or the upgrade page, I simply get a runtime error page:

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>
My host is simply a friend who hosts my site (and a few other sites) off his own server on his home connection, so although he does know what he is doing, I can't really contact him and get it fixed immediately, and I would prefer to try and fix it myself without having to rely on him to fix it every time something like this happens..

I only have web and ftp access to his server (ftp is for my site only).

I've tried backing up the web.config file, then editing it to show errors remotely, but this doesn't seem to have worked either.

I would asume i'm looking at a complete reinstallation to fix whatever went wrong, but i'm unsure how to proceed while preserving the site setup and layout.

Does anyone know how to fix this?

 
New Post
1/17/2010 5:51 PM
 

Your first step is to edit the site's web.config file to set:

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

When you next try to navigate to the site you should be able to see details of the actual error. Please post the entire error message to this forum.

Had you taken a complete backup of all of the site's files AND the database prior to the upgrade?

As for system requirements, note that DNN 5.2.1 now REQUIRES MS SQL Server 2005 (express or standard) or later and that ASP.Net 3.5 be installed on the server.


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
1/17/2010 6:13 PM
 

My friend has just got in, and he's got the error message for me from the server:

Parser Error Message: The file '/App_Code/DesktopModules/Admin/Security/ProfileDefinitions.ascx.vb' is in the special directory 'App_Code', which is not allowed.

I did not take a backup of my site or database before doing the upgrade, as 1) I have never run into this problem before when upgrading, and 2) It's only a personal site, so I could start again if I needed to, although it would be inconvenient. I also have no access to the database to back it up.

From looking at the requirements, it appears as though it has the same requirements as 05.02.00, which is what I was running before with no problems.

 
New Post
1/18/2010 6:59 AM
 

it looks like you did not extract / copy over files properly to the correct locations, there are no files to be copied into app_code folder, module files inside are created by the extension installer only.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade from 05.02.00 to 05.02.01 failedupgrade from 05.02.00 to 05.02.01 failed


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