Home > Programming, Windows > IIS7 Web Routing With Classic Managed Pipeline Mode: Failed to Execute URL

IIS7 Web Routing With Classic Managed Pipeline Mode: Failed to Execute URL

My head has been turning around for days with the exception “Failed to Execute URL”.

Background:
I have web routing configured for IIS 6 in production using a wild card entry.
It works well and was a hustle free setup.
But on the development machine I was running IIS 7 in intergrated mode, still web routing worked perfectly Not until we decided to align production and development. That meant switching dev machines to use Classic Managed Pipeline mode from intergrated mode.

To allow System.Web.Routing to work in IIS 7 Classic mode I did the following steps:

  1. Go the Handler Mappings, add a new mapping with
    Request Path: *
    Executable: %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
    Name: wild card
    Request Restrictions: Uncheck Invoke handler only if request is mapped to
    Verbs: All
    Click OK
  2. Click View ordered List
    Use the Move Up and Move down buttons to ensure that the mapping created above is below the Static file mapping.
  3. Click View Unordered List
    If you list is already unordered, that button will not appear.
    Select the Static file Mapping and Click Edit
    Change the Request Path to *.*
    Change the Request restrictions such that for the Invoke handler only if request is mapped to: File is selected.
    Click OK
  4. Restart IIS
    Browse the URL

On browsing the root URL, I get the following Error though when I browse the root + default document (e.g http://localhost/default.aspx) it works perfectly.

Failed to Execute URL

Failed to Execute URL

Am still trying to find why the default document module in this  case is not working.

Advertisements
Categories: Programming, Windows
  1. Shane
    January 25, 2011 at 8:36 am

    wondering if you ever found a resolution to this, I am having no luck trying to sort this one out?

    Cheers

  2. Joseph Ssenyange
    January 25, 2011 at 9:04 am

    No, never got it to work.
    We decided to migrate all production machines to windows server 2008 and decided to use integrated mode. But I never got it to work in classic managed pipeline mode

  3. Shane
    January 28, 2011 at 5:14 pm

    ok cheers

    I think I finally got it to work using the following handlers config. So far it seems to be working anyway.

  4. Shane
    January 28, 2011 at 5:17 pm

    ttempt 2 at posting sucessful config

    <handlers>
    <clear />
    <add name=”StaticFile”
    path=”/” verb=”*”
    modules=”DefaultDocumentModule”
    resourceType=”Either” requireAccess=”Read” />
    <add name=”PageHandlerFactory-ISAPI-2.0″
    path=”*” verb=”GET,HEAD,POST,DEBUG”
    modules=”DefaultDocumentModule,IsapiModule”
    scriptProcessor=”%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll”
    preCondition=”classicMode,runtimeVersionv2.0,bitness32″ responseBufferLimit=”0″ />

    </handlers>

  5. Joseph Ssenyange
    January 28, 2011 at 5:26 pm

    Cool…
    I will try it out.
    Thanks

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: