I have an installation of DNN with a number of portals I wish to upgrade to 4.5.6 from 4.4.1. I decided to run a dev server to test the new version with existing modules. After many hassles, I created the development server on a fresh database and successfully tested a number of the portals. Then I upgraded. All went ok but for a couple modules I forgot to unzip first. These passively failed and everything seemed ok. However, clicking "return to portal" - the app hung. I ran Process Explorer and Fiddler to discover DNN compiles then gets stuck in an infinite loop: www.mydomain.com/ 302 redirects to /Default.aspx?aliase=www.mydomain.com.I understand the need to be highly accurate in the portal alias table and to restart the application after making a manual change to the table. I can confirm many variations of the domain have been supplied and the entire start up process ran a number of times. I have one spare domain to test on but I hijacked another client's domain for a second and got the same results. Process explorer shows the process is constantly looking for httpd.ini (required by ISAPI_rewrite). I deleted the files/rules in both the server and websites versions of httpd.ini to eliminate ISAPI_rewrite as a source. I use human friendly URLs by Ventrian Systems so I tried with and without Scott's modified dll. I got nothing. Where do I start to look? |