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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving site from II6 to IIS7 - PORTAL ERRORMoving site from II6 to IIS7 - PORTAL ERROR
Previous
 
Next
New Post
11/25/2010 6:30 PM
 
I successfully moved seven single portal DNN 5.06 sites from Server 2006/IIS6 to Server 2008/IIS7 all using SQL Express 2008.

Two additional sites did NOT move successfully. Both of these sites are milti-portal [two each]. Navigating to either of these sites results in the error below: 

I double checked the bindings and all other site setting they all look correct. I checked the portalalias table and the entries there appear to be in order but I am not that familiar with DDN tables so I may need to alter something.

I look forward to a little help - thank you - Robert Baker

==================== 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) +50
   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/25/2010 10:56 PM
 
That is a familiar error that has been seen following an upgrade to or a new installation of DotNetNuke 5.06.00 on some sites - I am still trying to determine under what circumstances it occurs. There were a number of changes made to code in the UrlRewriteModule in v 5.06.00, primarily to implement automatic portal alias mapping for single portal sites.

Were these sites all upgraded from earlier DNN versions to 5.06.00 or were some new installs of 5.06.00?
If upgrades, were the upgrades all done prior to the server migration or afterwards?
Can you confirm that the errors did not occur prior to the server migration?

It is especially interesting to note that this only occured on the multi-portal sites.

Unfortunately, I have no work-around to offer at this time so you will most likely want to restore the two sites back to their pre-upgrade version (if the were in fact upgrades) and server location if possible. The issue (as well as a couple of other variations in behavior leading to the same error) have been logged in Gemini and engineering is working on it.

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
11/26/2010 10:58 AM
 
William,

Thank you for your quick response. Here are the answers to your questions:

Were these sites all upgraded from earlier DNN versions to 5.06.00 or were some new installs of 5.06.00?

· No new installs – all sites were simply moved straight up from IIS 6 to IIS7

If upgrades, were the upgrades all done prior to the server migration or afterwards?

· I moved all nine sites first.

· Seven converted perfectly so I then upgraded the seven single portal sites from 5.05 to 5.06 without issue.

· Two sites failed giving me the error message I provided.

· I attempted to upgrade the two failed sites to 5.06 hoping that it might fix things but I got the same error message.

Can you confirm that the errors did not occur prior to the server migration?

· Prior to the move all nine sites were working without issue on the old server. I moved them due to a failure to perform by my former ISP/

It is especially interesting to note that this only occurred on the multi-portal sites.

· Verified – absolutely the problem only exists with the multi-portal sites.

I can easily re-create one of the two multi-portal sites as there has not been much done; however, I really need to get the two portals on the other site running before Monday. I there any way to split the two portals into theri own sites?

Thank you,

Robert Baker
 
New Post
11/26/2010 12:46 PM
 
Robert,

Thanks for the answers to my questions. I have one more for you . . .

Were any of the sites running under ASP.Net 4.0 prior to the migration or are they now running in an ASP.Net 4.0 AppPool following migration to the new server? I ask this because in another thread this morning it was reported that changing back from ASP.Net 4.0 to 2.0/3.5 and backing out the ASP.Net 4.0 specific changes that had been made to the web.config corrected the issue for now. From what I know of the problem  I'm not so sure that is true.

In regards to your last question about splitting one of the multi-portal sites into separate single-portal installs:

It is possible but not easy - the basic procedure is to clone the installation (filesystem and database) then delete one portal from the first installation and the other portal from the second installation.

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
11/27/2010 8:20 PM
 
William,

Both sites were running under ASP.Net 4.0 to 2.0 / IIS 6. I managed to sucessfully restore one of them from a backup, back to the old server [Server 2006 IIS 6]. I am currently in the process of restoring the second site. The old server is painfully slow and I mean really painfull; the restore this site took over an hour. Once I get the second one running I'd like to move both of them to my new server and upgraded them from 5.05 to 5.06. What recommendations migth you suggest?

Thank you,

Robert Baker
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving site from II6 to IIS7 - PORTAL ERRORMoving site from II6 to IIS7 - PORTAL ERROR


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