ASP.NET MVC on IIS 6 - wildcard mapping - the incoming request does not match any route

Question

Hi,

I have been trying to set up my Beta 1 MVC app on IIS 6 and cannot get it to run correctly. I have added a Wildcard mapping to the .net isapi DLL as suggested in other blog posts but get the following error when I access the root of the website:

The incoming request does not match any route.
..
[HttpException (0x80004005): The incoming request does not match any route.]
   System.Web.Routing.UrlRoutingHandler.ProcessRequest(HttpContextBase httpContext) +147
   System.Web.Routing.UrlRoutingHandler.ProcessRequest(HttpContext httpContext) +36
   System.Web.Routing.UrlRoutingHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context) +4
   HCD.Intranet.Web.Default.Page_Load(Object sender, EventArgs e) +81
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

I am using the Default.aspx page supplied in the MVC template application that rewrites access to the root of the website properly.

public partial class Default : Page
{
    public void Page_Load(object sender, System.EventArgs e)
    {
     HttpContext.Current.RewritePath(Request.ApplicationPath);
     IHttpHandler httpHandler = new MvcHttpHandler();
     httpHandler.ProcessRequest(HttpContext.Current);
    }
}

If I try and access a route within the application, such as /Project, I get the standard IIS 404 error page, not the .net error page.

I tried adding the following line to my Web.config httpHandlers section:

<add verb="*" path="*" validate="false" type="System.Web.Mvc.MvcHttpHandler, System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

This gave me a different error - the .net 404 error page.

I added the following to my Global.asax, which did nothing:

protected void Application_BeginRequest(object sender, EventArgs e)
{
    if (Context.Request.FilePath.Equals("/"))
     Context.RewritePath("Default.aspx");
}

I am using the following route configuration (uses the restful routing supplied by the MvcContrib project):

routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
SimplyRestfulRouteHandler.BuildRoutes(routes);
routes.MapRoute(
"Default", 
"{controller}/{action}/{id}",
new { controller = "Home", action = "Index", id = "" }
);

Any suggestions would be grealy received as I've exhausted all options for the time I have right now.

Many thanks.

Answer 1

Unfortunatly IIS 6 needs a file extension to map the request to the right handler which means you will have to use the .mvc suffix on your controller names, such as /{controller}.mvc/{action}

routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

SimplyRestfulRouteHandler.BuildRoutes(routes);

routes.MapRoute(
      "Default",
      "{controller}.mvc/{action}/{id}",
      new { controller = "Home", action = "Index", id = "" }
);

However, the are ways around this depending on your level of control on the IIS 6 server. Please refer to the following pages for more information

• http://biasecurities.com/blog/2008/how-to-enable-pretty-urls-with-asp-net-mvc-and-iis6/
• http://www.flux88.com/UsingASPNETMVCOnIIS6WithoutTheMVCExtension.aspx

Answer 2

Thanks for the reply but I read articles similar to the ones you posted and they all said I can either enable wildcard mapping or install a rewrite module. Is this not the case and wilcard mappings just don't work? Contrary to what the articles say?

I was trying not to go down the .mvc extension method but maybe I'll need this.

Thanks again.

Answer 3

Here's what I did to get extensionless URLs working with IIS 6 and ASP.NET MVC Beta 1.

• Create a default ASP.NET MVC Beta project and compile it.
• Create a new IIS website pointing to the application directory.
• In the IIS properties for the website, click the HomeDirectory tab.
• Click the "Configuration..." button. In the "Mappings" tab, click "Insert..."
• Next to the "Wildcard application maps" label In the textbox, type in "c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll"
• Uncheck the box labelled "Verify that file exists" Click OK
• Navigate to /home It worked!

You shouldn't need to change web.config at all. You just need to map all requests to IIS to the ASP.NET Isapi dll otherwise ASP.NET will never get those requests.

Answer 4

Hi Phil, thanks for the response.

Did everything you suggested and when I browse to the site I get:

"The incoming request does not match any route".

If I browse to /Home I get the IIS 404, not the .Net one.

???

Is there anything I can send you so you have more to go on/investigate? Obviously something wrong with my version of IIS but not sure what at present.

Answer 5

I'm getting exactly the same symptoms. The weird thing is, if I create a new MVC project (using the basic template) then the deployed site works fine.

However, deploying the application I've built using that template is failing with the symptoms you describe.

I'm currently trying to figure out the different between the two (although I'm really not doing anything unusual).

Answer 6

OK, got it working.

The problem was that I was using msbuild automation to package up the files that I needed to deploy, and I was missing global.asax.

So it looks like if global.asax is not deployed to the site then none of the routes get hooked up. This means that hitting the website root correctly results in the error 'The incoming request does not match any route.', and any other requests no longer get routed through to your controller classes, so result in a 404.

HTH.

Answer 7

Hello, there is an alternative solution http://www.codeproject.com/KB/aspnet/iis-aspnet-url-rewriting.aspx