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...Keep getting "Upgrading DotNetNuke" messageKeep getting "Upgrading DotNetNuke" message
Previous
 
Next
New Post
12/1/2010 6:50 PM
 
Hello,

I have upgraded my DNN long ago to version 4.9.5. However, I keep getting periodically a "Upgrading DotNetNuke" message (see below) when trying to access my site. How do I get rid of this?

Thanks

Upgrading DotNetNuke

Current Assembly Version: 04.09.01

Current Database Version: 04.09.05



Upgrade Status Report

00:00:00.015 - Upgrading to Version: 4.9.1
00:00:00.015 - Performing General Upgrades

Upgrade Complete

 
New Post
12/1/2010 7:11 PM
 
It is very odd to see an assembly version (04.09.01) that is lower than the database version 04.09.05 as in an actual upgrade sequence, the copy of the upgrade files (including the new DotNetNuke.dll assembly)  over the existing site occurs prior to the upgrade of the database. I suspect that the v 04.09.05 DotNetNuke.dll assembly might have been accidentally replaced by the older v 04.09.01 assembly at sometime following the upgrade - may via FTP or by installation of a module which had been compiled against the 04.09.01 version and which incorrectly included the old DotNetNuke.dll in its package.

Have you checked the Event Viewer for other errors that may be related to a version mis-match between the DotNetNuke assembly and the database?

Replacing the v 04.09.01 DotNetNuke.dll file (in folder /bin) with the correct version from a 04.09.05 install package should take care of the problem BUT . . . I would first suggest comparing version information of other assemblies in the site's  /bin folder and also a few other key files with those in the 04.09.05 install package - just in case there is something more serious going on here.

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
12/1/2010 9:12 PM
 
I can't even see the event viewer logs. Could I just reinstall 4.9.5 on top of the current installation?
 
New Post
12/1/2010 9:26 PM
 
Although you are probably safe to extract the 4.09.05 UPGRADE package over the existing site installation, I would first suggest trying to replace only the DotNetNuke.dll file in the site's /bin folder with that extracted from the 4.09.05 Upgrade package.

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
12/1/2010 10:23 PM
 
Hi William, I did as suggested and replaced the DotNetNuke.dll file from the 4.09.05 Upgrade package in to the /bin folder and get the following error. Not sure what to do now.

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 tag within a "web.config" configuration file located in the root directory of the current web application. This 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 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>
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Keep getting "Upgrading DotNetNuke" messageKeep getting "Upgrading DotNetNuke" message


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