We are moving all of our web servers over to Server 2008 / IIS7 and have ran into one last snag. AJAXUploader throws the error below when IIS7 is set to use Integrated mode rather than classic. When the app pool is set to classic it works fine, but when set to integrated it does not. I have downloaded the latest version but this did not fix the problem.
Is there any other fix other then switching to the much slower classic mode?

Error:

EO.Web Controls Client Side Debug Message:
EO.Web control 'ctl00_cpMain_fuFiles' error message (set ClientSideOnError to handle this error):EO.Web.Runtime must be added into your web.config's httpModules section because another HttpModule (Usually FormsAuthenticationModule) fetched the upload data before it reaches AJAXUploader. Please see "Using AJAXUploader" in the help file for details.
You can turn off this message by setting EO.Web.Runtime.DebugLevel to 0 (Not recommended for debug build).

I have the settings it discusses in the web.config
<httpModules>
<add name="EOWebRuntime" type="EO.Web.Runtime,EO.Web" />
<add name="Identity Federation Service Logon Server Authentication Module" type="System.Web.Security.SingleSignOn.WebSsoAuthenticationModule, System.Web.Security.SingleSignOn, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35, Custom=null" />
<add name="Identity Federation Services Application Authentication Module" type="System.Web.Security.SingleSignOn.WebSsoAuthenticationModule, System.Web.Security.SingleSignOn, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null" />
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
</httpModules>

---

David L. Sargent
Developer
Washington State University

I just realized how to fix it. We use ADFS / Single Sign on from Microsoft, this too had problems in IIS7 Integrated mode, the fix was (from MS tech support) was to add the ADFS ref in
<system.webServer>
<modules>
I thought I'd give that a shot with the EO control and it worked.
So the following code seems to fix the problem
<system.webServer>
<modules>
<add name="EOWebRuntime" type="EO.Web.Runtime,EO.Web" />
</modules>

The following is a quote from the MS tech.
"I had a closer look at the web.config deployed by running the appcmd migrate command in our test lab and it had performed the exact same operation on the web.config as what your customer had seemed to have done.

I, therefore, would suggest running the migrate command as the recommended action for this issue.

Here is some background on why this is needed.

The implementation of the Integrated Pipeline mode for the application pool is a new feature in IIS 7.0, while the classic is the older mode supported in IIS 6.0.
At the time the sample apps were written, this was configured for applications running host on IIS 6.0 using this classic mode of operation.

Thus, running the application in *newer* integrated mode in IIS 7.0 requires a migration of this configuration by redefining our sign in module as a module within the System.webServer tag. This seems to be a generic migratory step in order to any application (configured to use a httpmodule) to migrate and work in the integrated pipeline mode from classic."

Hope that helps!

---

David L. Sargent
Developer
Washington State University