(Ektron CMS 400.Net,Microsoft IIS,Microsoft ASP.NET)
by Jason Skowronek
on 10/21/2009
I recently came across a scenario where we had to configure a separate virtual application under our Ektron site. As you are aware, Ektron is heavy with it's own HttpHandlers and modules. This is the contents of a bare-bones web.config file you can drop into your virtual application directory to disable the offending Ektron DLLs from running and failing.
Update 1:
I ran across a KB article posted by Ektron on this topic as well. They offer a more in-depth list of modules/handlers to disable in the web.config.
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.web>
<customErrors mode="Off">
</customErrors>
</system.web>
<system.webServer>
<handlers>
<remove name="ek*" />
<remove name="ekdav" />
<remove name="EktronWorkflowImage" />
</handlers>
<modules>
<remove name="MyDigestAuthenticationModule" />
<remove name="EkUrlAliasModule" />
</modules>
</system.webServer>
</configuration>