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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Web.Config UpdatesWeb.Config Updates
Previous
 
Next
New Post
1/21/2009 10:21 PM
 

So I tried the approach of letting the upgrade make the changes to my existing web.config file.

At first I got a permission error and had to set NETWORK SERVICE permissions.

I updated the permissions and ran the upgrade again. Here is what I got.

Upgrading DotNetNuke
Current Assembly Version: 04.09.01
Current Database Version: 04.05.05

Upgrade Status Report
00: - Upgrading to Version: 4.9.1
00:00:00.015 -   Executing Script: 04.06.00.SqlDataProvider Error! (see 04.06.00.log for more information)
00:00:00.609 -   Executing Script: 04.06.01.SqlDataProvider Success
00:00:00.640 -   Executing Script: 04.06.02.SqlDataProvider Success
00:00:00.640 -   Executing Script: 04.07.00.SqlDataProvider Error! (see 04.07.00.log for more information)
00:00:01.062 -   Executing Script: 04.08.00.SqlDataProvider Success
00:00:01.234 -   Executing Script: 04.08.01.SqlDataProvider Error! (see 04.08.01.log for more information)
00:00:01.453 -   Executing Script: 04.08.02.SqlDataProvider Success
00:00:01.500 -   Executing Script: 04.08.03.SqlDataProvider Success
00:00:01.500 -   Executing Script: 04.08.04.SqlDataProvider Success
00:00:01.515 -   Executing Script: 04.09.00.SqlDataProvider Error! (see 04.09.00.log for more information)
00:00:01.609 -   Executing Script: 04.09.01.SqlDataProvider Success
00:00:02.265 - Performing General Upgrades

Upgrade Complete

Click Here To Access Your Portal

When I tried to access the portal I got this error.

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.Security.Membership.AspNetMembershipProvider.GetUserCountByPortal(Int32 portalId) +9
   DotNetNuke.Entities.Portals.PortalInfo.get_Users() +28
   DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +1726
   DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +76
   DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2165
   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.3053; ASP.NET Version:2.0.50727.3053

Thanks for any ideas on what I could have done wrong.

 


Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
1/21/2009 10:43 PM
 

Note that for xmlmerge to properly manage changes to your web.config, the site that you are upgrading must be DNN version 4.06.02 or later. It appears that the site you were attempting to upgrade is 4.05.05. If possible, I would roll back to your files and db backup then upgrade first to DNN 4.6.2 using the old approach of copying over the appropriate sections from your existing web.config.

If roll back is not possible, have you taken a look at the sql log files mentioned in the errors?

Also note that only the upgrade version should be used - not the install version since the upgrade version does not contain its own web.config file.


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
1/22/2009 11:21 AM
 

Thanks for the info. I already did the roll back last. night. I will pick a suitable upgrade level and do that and then do the final 4.9.1 upgrade using the xmlmerge approach.


Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Web.Config UpdatesWeb.Config Updates


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