ASP.NET 2.0 application never loads

I have an application that runs perfectly fine locally using the VS 2010 application server, however, when I deploy to our web app machine startup just spins and spins and never loads.开发者_Python百科 We have other apps on this same machine that load just fine (this is a debug deployment of same app in product).

I have been spinning my wheels on this for days and I am at a loss as the problem could be.

Here is what I did

1. Create a new directory (same level as other apps)
2. Copied over our existing test (www.domain/test/) and it works fine
3. Build and publish new debug app (www.domain/test/) and it just spins trying to load first form.

I know the diretory is "working" as the 'test' application I put there works fine.

If it's killing the App pool, you might get something in the event log. Fiddler (www.fiddlertool.com) is great http debug tool which let you see if you're in a redirect loop. Also Firefox shows a more meaningful error, something about exceeding the max redirect count.

It does sound like something is looping, but not quick enough to cause a stack overflow, which is odd, because you'd expect it to fail every time.

Simon

Do you have the ability to remote desktop into the machine? If so try running process explorer and look at the process details for the worker process that is giving you issues. Definitely look at the TCP connections being created. If your processor is pegged at 100%, and memory usage is rising then you probably have an endless loop running.

It sounds like it's more related to IIS than ASP.NET. What about the identity that the website is running under? Is it possible that the user the site's running under a bad user, or maybe the password needs to be re-entered?

I did a quick Bing search

There are a lot of postings regarding the error message you described above. Most if not all point to code in your app that is crashing. I know I had a similar problem when I used an automated/threaded daemon utility in my web application. Make sure your code is not bringing down the server, sometimes the VS2010 web server is a little more foregiving than an actual IIS deployment.

If that doesn't work try running a Remote Debugging Session to try and catch any errors being thrown but not handled.

Lastly you could try to setup a new local IIS server to see if you have the same problems. Scott Gu has a nice article about using IIS Express to do this.