infinite looping after upgrade - Snapsis Software - DotNetNuke Support Forums - DotNetNuke Support

infinite looping after upgrade

Last Post 08 Aug 2007 03:17 PM by llong. 2 Replies.

Sort:

	Prev Next
Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

llong

Basic Member

Posts:113

07 Aug 2007 04:51 PM
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?

John Mitchell
Administrator

Veteran Member

Posts:4384
Avatar

07 Aug 2007 11:22 PM
Is there any chance that you think you're pointing to the production Database server but you actually have the connection strings pointing at development, or maybe the other way around? I have got caught by that mistake when switching between dev and production more than once. If your main domain is redirecting to a url with alias in the querystring then you may be hitting a default.aspx page that is actually intended for a child portal. Check your default page to make sure that it does not just have redirect code in it.

llong

Basic Member

Posts:113

08 Aug 2007 03:17 PM
Thank you John, the default.aspx file was the source. I under estimated the function of that file which I had customized before.

Please Register to post a reply.

Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Active Forums 4.1