http://forums.iis.net/p/10
----
919789 How to use the Debug Diagnostics tool to troubleshoot an IIS process that stops unexpectedly
http://support.microsoft.c
---
Main Topics
Browse All TopicsI have an older ASP.NET 2.0 site that I'm attempting to port over to IIS 7. The application will not launch. There are no error messages, just a long hang in the browser, and eventually after enough attempts, a 503 error. The Server Event log shows the following error:
Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module kernel32.dll, version 6.0.6001.18000, time stamp 0x4791a76d, exception code 0xe053534f, fault offset 0x000442eb, process id 0x%9, application start time 0x%10.
I've attempted running the site in Classic Mode, in various other application pools, and always the same result. It doesn't even get to .NET it seems. I have a sister application that contains similar code that I ported to IIS 7 on another webserver, and despite a couple config migrations, everything is working fine.
I'm at a loss as to how to troubleshoot this, or if anyone else has had a similar experience.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
http://forums.iis.net/p/10
----
919789 How to use the Debug Diagnostics tool to troubleshoot an IIS process that stops unexpectedly
http://support.microsoft.c
---
Business Accounts
Answer for Membership
by: tradelinePosted on 2009-01-26 at 11:42:02ID: 23470009
This has been a real interesting problem: but here's a temporary hack for others who may stumble upon this:
If you can identify any page inside of the application that is an aspx page that doesn't cause the crash, login with that page as your returnurl, and then the site builds. After that point, I can logout and relogin as expected with everything working.
All pages worked after I did this, but the problem has not gone away, I just went around it. Naturally when I need to recompile again this is going to throw the same error, but at least the app is up now while I troubleshoot.