FYI integrated mode is the pre-requistite and is the only pipeline we test with - any errors discovered with classic mode will not be worked on

At a high level the problem is that classic mode on various Microsoft OS's can work subtely differently, in some cases even certain windows updates cause issues - whereas integrated pipeline works as expected on all versions i.e. the same set of actions and behaviours occur. This is particuarly important with newer technologies such as MVC (which was used in 6.2.0) and WebAPI (used in 7.x) where sometimes service requests will not work in classic mode depending on the IIS version/OS version/security and maitenance patches, but will work as expected in integrated mode. Essentially classic mode was a bit of a hack to maintain old behaviours in the new pipeline world, whereas integrated pipeline was written as new, so these inconsistencies are not surprising and hence our decision to require integrated mode.

As to your issue my understanding was that automatic doesnt work in 7.x (http://dnnauthad.codeplex.com/release... ) so the AD provider will need updated.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

one of the main differences between classic and integrated mode is that in classic mode only .net mapped requests (aspx/ascx/asmx etc.) are passed through the pipeline, whereas in integrated mode all requests are passed through. At a guess I would suggest that a non .net mapped request is causing an exception and causing the site to load. As this problem appears localised to your instance (i.e we have no similar reports in support.dotnetnuke.com) it would suggest some module/extension you are using (likely in combination with some configuration) is causing the issue. I'd recommed copying the site to a test environment (check it still fails in the same way), and try a process of elminiation (i.e. remove any non core http module/http handler references in web.config, remove any 3rd party dlls from the bin etc.) until you identify the failing element

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Well, after 3 weeks and thousands of dollars burned we've decided to just roll back to 5.X and not mess with it for the time being. My client is going to look into other frameworks (I'm not sure what's availalbe) as DNN has cost them over 10 grand now and they still do not have a functioning site. Thanks you for your help - I may be back if they decide to stick with DNN - a recomendation I certainly can not make, but ultimately it's up to them. They've invested a lot of time in some LMS modules that they likely can't stomach throwing away.