Have identified a few additional 'head scratching' challenges with regards to this issue.

If I go directly via the 'Host' menu to:

(replacing my domain name with domain.com for security reasons)

http://domain.com/Host/Portals/tabid/17/portalid/0/Default.aspx

It redirects me to the http://domain.com and does not take me to the appropriate page.

However, if I click on a different page within the 'Host' menu option for instance 'Module Definitions' and wait for the page to load and then change only the tabid from 18 to 17 as shown below:

http://mydomain.com/Host/Module%20Definitions/tabid/17/portalid/0/Default.aspx

I am able to successfully get to the Portals page.  However, once I get to the portals page if I want to 'Add' a new portal and click on Add Portal I am then redirected back to the home page http://mydomain.com again.

However, I went to another site I have which is running version 5.2.3 and found out the url which is rendered when clicking 'Add New Portal' and pasted the following after http://mydomain.com as show below:

/tabid/17/ctl/Signup/mid/321/portalid/0/Default.aspx

I can then add a new portal to the Host.  There must be something in the Core which is causing this error to occur.  I have never seen it before and have never had a problem until this 5.5 upgrade.

These upgrades lately have been quite challenging.  It seems like one thing works, another is broken, the broken part gets fixed and something that use to work now is broken.  I understand software a bit and this seems to be out of the ordinary.  I am hoping someone has a solution.

Dennis,

Not sure if it can helps, just suggestion:
1. Open your Portals page with direct URL you have
2. Go to module settings, choose "Page Settings > Advanced Settings" and move this module to any other page.

---

Papayas DnnAutoUpgrade - automatic DotNetNuke upgrade without any problems!
www.papayasdnn.com