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...Any solutions to Object reference not set to an instance of an object. After upgradeAny solutions to Object reference not set to an instance of an object. After upgrade
Previous
 
Next
New Post
1/12/2011 8:05 PM
 
I upgraded today from 4.05 -> 4.06.02 -> 4.09.05 without any errors.
However,  4.09.05 -> 5.04.04 had some errors and now I get the following on the site.  I see others have gotten this error, but I have yet to find a solution. 

Anyone have some ideas as to what to try?


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:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.Entities.Portals.PortalInfo.get_Pages() +38 DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 tabID, PortalInfo portal) +938 DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) +113 DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2176 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 


Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3618



Upgrade Page

Upgrading DotNetNuke

Current Assembly Version: 05.04.04

Current Database Version: 04.09.05



Upgrade Status Report

00:00:00.109 - Upgrading to Version: 05.04.04
00:00:00.328 -   Executing Script: 05.00.00.SqlDataProvider Success
00:00:09.453 -   Executing Script: 05.00.01.SqlDataProvider Success
00:00:10.140 -   Executing Script: 05.01.00.SqlDataProvider Success
00:00:13.890 -   Executing Script: 05.01.01.SqlDataProvider Success
00:00:14.249 -   Executing Script: 05.01.02.SqlDataProvider Success
00:00:14.281 -   Executing Script: 05.01.03.SqlDataProvider Success
00:00:14.374 -   Executing Script: 05.01.04.SqlDataProvider Success
00:00:14.390 -   Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log.resources for more information)
00:00:15.296 -   Executing Script: 05.02.01.SqlDataProvider Error! (see 05.02.01.log.resources for more information)
00:00:15.484 -   Executing Script: 05.02.02.SqlDataProvider Error! (see 05.02.02.log.resources for more information)
00:00:15.578 -   Executing Script: 05.02.03.SqlDataProvider Success
00:00:15.624 -   Executing Script: 05.03.00.SqlDataProvider Error! (see 05.03.00.log.resources for more information)
00:00:16.734 -   Executing Script: 05.03.01.SqlDataProvider Success
00:00:16.765 -   Executing Script: 05.04.00.SqlDataProvider Error! (see 05.04.00.log.resources for more information)
00:00:17.453 -   Executing Script: 05.04.01.SqlDataProvider Success
00:00:17.515 -   Executing Script: 05.04.02.SqlDataProvider Success
00:00:17.671 -   Executing Script: 05.04.03.SqlDataProvider Success
00:00:17.765 -   Executing Script: 05.04.04.SqlDataProvider Success
00:00:17.796 -   Executing Application Upgrades: 05.00.00 Error!
00:00:18.062 -   Executing Application Upgrades: 05.00.01 Success
00:00:18.156 -   Executing Application Upgrades: 05.01.00 Error!
00:00:18.203 -   Executing Application Upgrades: 05.01.01 Success
00:00:18.234 -   Executing Application Upgrades: 05.01.02 Success
00:00:18.234 -   Executing Application Upgrades: 05.01.03 Success
00:00:20.343 -   Executing Application Upgrades: 05.01.04 Success
00:00:20.343 -   Executing Application Upgrades: 05.02.00 Error!
00:00:21.796 -   Executing Application Upgrades: 05.02.01 Success
00:00:21.812 -   Executing Application Upgrades: 05.02.02 Success
00:00:21.812 -   Executing Application Upgrades: 05.02.03 Success
00:00:21.812 -   Executing Application Upgrades: 05.03.00 Error!
00:00:22.156 -   Executing Application Upgrades: 05.03.01 Success
00:00:22.156 -   Executing Application Upgrades: 05.04.00 Error!
00:00:22.906 -   Executing Application Upgrades: 05.04.01 Success
00:00:22.906 -   Executing Application Upgrades: 05.04.02 Success
00:00:22.906 -   Executing Application Upgrades: 05.04.03 Success
00:00:23.546 -   Executing Application Upgrades: 05.04.04 Success
00:00:23.546 -   Cleaning Up Files: 05.00.00 Success
00:00:24.327 -   Cleaning Up Files: 05.00.01 Success
00:00:24.359 -   Cleaning Up Files: 05.01.00 Success
00:00:24.562 -   Cleaning Up Files: 05.01.01 Success
00:00:24.562 -   Cleaning Up Files: 05.01.02 Success
00:00:24.562 -   Cleaning Up Files: 05.01.03 Success
00:00:24.562 -   Cleaning Up Files: 05.01.04 Success
00:00:24.562 -   Cleaning Up Files: 05.02.00 Success
00:00:24.562 -   Cleaning Up Files: 05.02.01 Success
00:00:24.562 -   Cleaning Up Files: 05.02.02 Success
00:00:24.562 -   Cleaning Up Files: 05.02.03 Success
00:00:24.562 -   Cleaning Up Files: 05.03.00 Success
00:00:24.593 -   Cleaning Up Files: 05.03.01 Success
00:00:24.593 -   Cleaning Up Files: 05.04.00 Success
00:00:24.593 -   Cleaning Up Files: 05.04.01 Success
00:00:24.593 -   Cleaning Up Files: 05.04.02 Success
00:00:24.593 -   Cleaning Up Files: 05.04.03 Success
00:00:24.593 -   Cleaning Up Files: 05.04.04 Success
00:00:24.593 -   Updating Config Files: 05.00.00 Success
00:00:24.593 -   Updating Config Files: 05.00.01 Success
00:00:24.593 -   Updating Config Files: 05.01.00 Success
00:00:24.624 -   Updating Config Files: 05.01.01 Success
00:00:24.624 -   Updating Config Files: 05.01.02 Success
00:00:24.624 -   Updating Config Files: 05.01.03 Success
00:00:24.624 -   Updating Config Files: 05.01.04 Success
00:00:24.624 -   Updating Config Files: 05.02.00 Success
00:00:24.656 -   Updating Config Files: 05.02.01 Success
00:00:24.671 -   Updating Config Files: 05.02.02 Success
00:00:24.671 -   Updating Config Files: 05.02.03 Success
00:00:24.671 -   Updating Config Files: 05.03.00 Success
00:00:24.702 -   Updating Config Files: 05.03.01 Success
00:00:24.702 -   Updating Config Files: 05.04.00 Success
00:00:24.702 -   Updating Config Files: 05.04.01 Success
00:00:24.702 -   Updating Config Files: 05.04.02 Success
00:00:24.702 -   Updating Config Files: 05.04.03 Success
00:00:24.702 -   Updating Config Files: 05.04.04 Success
00:00:24.702 - Performing General Upgrades




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.Entities.Tabs.TabController.GetTabsByNameAndPortal(String TabName, Int32 PortalId) +72 DotNetNuke.Entities.Tabs.TabController.GetTabByNameAndParent(String TabName, Int32 PortalId, Int32 ParentId) +19 DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +55 DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, Version dataBaseVersion) +1046 DotNetNuke.Services.Install.Install.UpgradeApplication() +950 DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +272 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627 


Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3618
 
New Post
1/12/2011 8:28 PM
 
Looks as a timeout.  Restore database and the updatepackage and retry it.  This issue caused often if the server is to low, or other applications used to much resources.
 
New Post
1/12/2011 10:14 PM
 
I have restored the DB and tried the upgrade 3 times now with the same results.  The only thing I can think of right now is try a lower or higher upgrade version.  I think I have seen this error before when portal the alias is wrong but I checked the DB and it has not changed.  Does 5.x.x run on sql 2000?
 
New Post
1/12/2011 10:57 PM
 
That may be the problem as the first SQL error was when running the 05.02.00.SqlDataProvider script. DotNetNuke versions 5.02.00 and later require MS SQL Server 2005 or 2008 (standard or express) rather than SQL Server 2000. Also, even if you have upgraded to MS SQL 2005 or 2008, make sure that the database compatibility mode is set for 90 or 100 respectively.

Also, note that DotNetNuke version 5.02.00 and later require ASP.Net 3.5 SP 1. Versions 5.04.00 and up can also use ASP.Net 4.0.

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
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Any solutions to Object reference not set to an instance of an object. After upgradeAny solutions to Object reference not set to an instance of an object. After upgrade


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