http://www.w3.org/TR/xhtml1/DTD/xht...tional.dtd">
http://www.w3.org/1999/xhtml">
< le>Un led Document
I am getting an error when trying to perform an upgrade - can anyone give any insight on this:
Upgrading DotNetNuke
Current Assembly Version: 05.05.00
Current Database Version: 05.04.04
Upgrade Status Report
00:00:00.031 - Upgrading to Version: 05.05.00
00:00:00.031 - Performing General Upgrades
body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
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:
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.En ies.Tabs._Closure$__9._Lambda$__18(TabInfo t) +14 System.Linq.WhereSelectListIterator`2.MoveNext() +4181384 System.Linq.Enumerable.FirstOrDefault(IEnumerable`1 source) +4187840 DotNetNuke.En ies.Tabs.TabCollection.WithTabName(String tabName) +135 DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +78 DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, Version dataBaseVersion) +842 DotNetNuke.Services.Install.Install.UpgradeApplication() +949 DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +367 System.Web.UI.Control.OnLoad(EventArgs e) +91 System.Web.UI.Control.LoadRecursive() +74 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207 |
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1