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 problems from 4.9 to 5.10Upgrade problems from 4.9 to 5.10
Previous
 
Next
New Post
6/25/2009 12:52 PM
 

Hi, has anyone got any ideas?

I have tried a couple of times today to do a straight forward upgrade to 5.1. I had tried to upgrade earlier this year to 5.01 but couldn't get it to work at all. This time it has been different; during the upgrade the browser showed the following error. I refreshed the page after and the application worked. It allowed me to log back in as host and found that the XMods were fine but other vendor PA's namely Live Content were showing errors. I thought thought I would need to install recent PA for DNN5.0 but when I went to the module definitions page this was the errors I found.

I am not a technical expert just a keen amateur. 

 

Current Database Version: 04.09.01
 
Upgrade Status Report
00: - Upgrading to Version: 05.01.00
00:00:00.078 -   Executing Script: 05.00.00.SqlDataProvider 
Error! (see 05.00.00.log for more information)
 

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>

 

 And then this error on the host menu - module definitions page

 Error: Module Definitions is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The file '/Admin/ModuleDefinitions/ModuleDefinitions.ascx' does not exist. ---> System.Web.HttpException: The file '/Admin/ModuleDefinitions/ModuleDefinitions.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

 

 

Error: Module Definition Validator is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The file '/Admin/ModuleDefinitions/ModuleDefValidator.ascx' does not exist. ---> System.Web.HttpException: The file '/Admin/ModuleDefinitions/ModuleDefValidator.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

Is this installation salvageable or should I revert back to 4.9?

Thanks

 

 
New Post
6/30/2009 7:02 AM
 

I experience the same problem. It's also happening for the Languages and Skins module. The Extensions icon in the Control Panel is grayed out and the Extensions menu item is missing from the Host menu.

 
New Post
7/9/2009 6:32 AM
 

I have exactly the same issue.

Any fix yet for this?

 

Catalin

 
New Post
7/9/2009 7:35 AM
 

make sure to unzip all files from upgrade package hierarchically into the DNN installation folder, overwriting existing files.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/13/2009 6:52 PM
 

I'm having the exact same problem, but the suggested fix didn't work.  I extracted both the upgrade and the install for 5.10, but neither produced any different results.  Could this be a data issue? 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade problems from 4.9 to 5.10Upgrade problems from 4.9 to 5.10


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