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...5.5.1 to 5.6.0 upgrade - Sites dead at root-level, fine below5.5.1 to 5.6.0 upgrade - Sites dead at root-level, fine below
Previous
 
Next
New Post
11/19/2010 5:28 AM
 

Upgraded from 5.5.1 to 5.6.0 without error.

After the obligatory recycles and restarts, the portals all display the error pasted below when browsed via their normal root domain. However, when the sites are browsed via sub pages, the sites work.
 
Browse www.domain.com = Fail
Browse www.domain.com/subpage.aspx = Fine
 
Being suspicious of the automatic alias mapping (what for?) I checked the alias table, but all seems fine in there.
 
I've restored everything back to 5.5.1 and will wait for 5.6.1 
Regards
Rob
 
This is the error message:
 
 

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.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) +49
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2332
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
 
New Post
11/19/2010 9:47 AM
 
Is your "UsePortNumber" setting commented out in web.config?
If yes, uncomment it and try with upgrade again.
I suppose it is the same issue: http://www.dotnetnuke.com/Resources/Forums/tabid/795/forumid/200/threadid/395775/scope/posts/Default.aspx

Papayas DnnAutoUpgrade - automatic DotNetNuke upgrade without any problems!
www.papayasdnn.com
 
New Post
11/19/2010 11:56 AM
 
Please, I am having the same problem
 
New Post
11/22/2010 7:36 PM
 
Please see this thread for one possible trigger and a partial work-around for this issue:

http://www.dotnetnuke.com/Resources/F...

It has also been added to Gemini support issues: http://support.dotnetnuke.com/issue/V...

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...5.5.1 to 5.6.0 upgrade - Sites dead at root-level, fine below5.5.1 to 5.6.0 upgrade - Sites dead at root-level, fine below


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