I copied the upgrade version of 4.8.3 over my existing site, and then browsed to it to do the upgrade. I have autoupgrade set to false, to I had to browse manually to Install/install.aspx.
Below is the "error" that was generated. But, I then browsed to the site and it happily thinks it's a 4.8.3 site, and so it must be. Why did I get the error?
---
Upgrading DotNetNuke
Current Assembly Version: 04.08.03
Current Database Version: 04.07.00
Upgrade Status Report
00:00:00.015 - Upgrading to Version: 4.8.3
00:00:00.031 - Executing Script: 04.08.00.SqlDataProvider Success
00:00:00.562 - Executing Script: 04.08.01.SqlDataProvider Success
00:00:00.781 - Executing Script: 04.08.02.SqlDataProvider Success
00:00:00.812 - Executing Script: 04.08.03.SqlDataProvider Success
00:00:00.812 - Performing General Upgrades
00:00:02.656 - Installing Package File LiveID_01.00.00_Install:
Server Error in '/' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. |
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Services.Localization.Localization.GetString(String name) +11
DotNetNuke.Services.Packages.Util.GetLocalizedString(String key) +5
DotNetNuke.Services.Packages.Util..cctor() +11
[TypeInitializationException: The type initializer for 'DotNetNuke.Services.Packages.Util' threw an exception.]
DotNetNuke.Services.Packages.InstallerInfo.ReadZipStream(Stream inputStream) +29
DotNetNuke.Services.Packages.InstallerInfo..ctor(Stream inputStream, String sitePath) +244
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.InstallPackage(String strFile, Boolean allowResources, Boolean writeFeedback, Int32 indent) +326
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent, String type) +937
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent) +16
DotNetNuke.Services.Install.Install.UpgradeApplication() +930
DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +292
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436
|