With the upgrade to 2.3.8.5 I noticed errors where I was running some legacy Classic ASP/.NET code that read like this:
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
The error message told me to add this code to the system.webserver section of the web.config.
validation validateIntegratedModeConfiguration="false"
The code was already in there, so that didn't help.
After lots of research and trying different things I found this article and the solution. I changed the web.config as instructed and the error went away.
http://runtingsproper.blogspot.com/2010/04/solved-iis7-validateintegratedmodeconfi.html
Go into the Mojo web.config, find the system.webServer area and change this code:
<location inheritInChildApplications="false">
<system.webServer>
<!-- Disable runtime rejection of Integrated mode applications that have legacy ASP.NET settings -->
<validation validateIntegratedModeConfiguration="false"/>
<defaultDocument>
<files>
TO THIS
<system.webServer>
<!-- Disable runtime rejection of Integrated mode applications that have legacy ASP.NET settings -->
<validation validateIntegratedModeConfiguration="false" />
</system.webServer>
<location inheritInChildApplications="false">
<system.webServer>
<defaultDocument>
<files>
Basically you have to add a second <system.webServer> section with just the validateIntegratedModeConfiguration="false" inside of it. The link above explains why this was necessary.
Joe, could you change this on your end or consider one of the other work-arounds mentioned in the article? I bet anyone running legacy code inside the same app pool will have this problem going forward otherwise (as of version 2.3.8.5). It appears that the newly added <location inheritInChildApplications="false"> code is cancelling out the validateIntegratedModeConfiguration="false"
Hope this helps someone else!