James,

Did the new entries in PortalAlias table contain "skins/minimalextropy" as part of their value? If so, I would try deleting all of the Portal Alias table rows that were not present before the upgrade.

---

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

There has been one other report in the forums of similar entries being added to the PortalAlias table following installation of DNN 5.06.00 in cases where the UsePortNumber setting element in web.config was comment out. Apparently the newly introduced automatic portal alias mapping introduced in 5.06.00 has a problem.

After you deleted all of the invalid portal aliases from the PortalAlias table, did you force a restart of the site (make insignificant change to web.config then resave or re-upload web.config)? The data in this table is heavily cached and sometimes difficut to clear from the cache without restarting the application.

If not, check the PortalAlias table again. I'd be interested to know if the invalid entries regenerated themseleves again. If so, delete them once again then force the restart of the site.

As for why ErrorPage.aspx is being displayed without an exception having triggered it, I don't know at this time.

---

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

Same problem here - Can't browse sites with root domain, but can browse sub pages.
Have no problems in alias table... no additionial entries.
The UsePortNumber line was commented out, so I tried it uncommented and it made no difference.
Rob