Hello, my update 5.2.3-> 5.5.1 did not run as expected. There was an error message: update 5.3.0 was not successful (red) - Everything else went fine (green). The problem is now that one of the domains is not accessible any more. I have one DNN installation with a few top level domains (Host > Portals) Portal Id --- Title --- Portal Aliases 0 --- domain 1 portal  le --- www.domain1.com 7 --- domain 1 portal  le --- www.domain2.com 8 --- domain 1 portal  le --- www.mydomain.com 4 --- domain 2 portal  le --- www.domain3.com The home directory column of the portals table (SQL Server) looks like: HomeDirectory Portals/0 MyDomain Portals/4 Portals/7 Checking the files on the server I can the see: DNNinstallationDirectory .admin .all the other DNN directories .MyDomain .Portals .._default ..0 ..4 ..7 The domains 1,2,3 are OK. If I want to go to "mydomain" I end up at domain1, which was the first domain created. The only difference I can see is that for "mydomain" the "home directory" is customised in Host > Portals > Add New Portal > Home Directory > Customise. This creates the portal directory as a top level directory. I think when I created the not working portal I gave it a descriptive name instead using the autogenerated DNN number. This apparently caused the creation of the "MyPortal" directory in the same directory level as "Portals". Any ideas why this would effect the access to the portal after the upgrades? Regards Oliver

If you made backups before upgrading, you can revert to the backups while you investigate the problem.

Were there any details regarding the error?

Hi Joe, thank you for the quick answer - yes I did a backup. However, the same error occurred when I upgraded from 5.2.3 to 5.4.xxx At this time, I had to roll back the upgrade due to work pressure. Now I have upgraded again - with the same result. At a certain point I HAVE TO solve this issue... ;-) I may as well try now.... The quick solution is to auto forward from domain1 home tab to www.mydomain.org.uk/Home/tabid/103/Default.aspx This is my temp fix. The main domain is available but only with the "long tail" not with www.mydomain.com (well... at the moment it is but not if I clear the auto forward of the home tab of domain1). domain1 is not available at the moment... Any idea why DNN suddenly after an upgrade does not resolve the domain properly? Three domains are working one does not.... Many Thanks. Oliver

Hello, i solved the problem.... reason for redirecting one domain to another domain on the portal were entries in the PortalLocalization table.

http://www.dotnetnuke.com/Community...guage.aspx

I do not know where these entries came from or who created them.... after deleting it all works fine. ;-O

Grest!