Error - Could not register wildcard mapping for aspnet_isapi.dll, file cound not be found.

Member since: 2009

I'm trying to install EPiServer CMS 5 R2 on a Windows 2003 web server, but I keep getting the error:

Error - Could not register wildcard mapping for aspnet_isapi.dll, file cound not be found.

The file on the server is located exactly where it should be:


I have searched hard to find a solution to this but found no texts that describe this error.

Thanks in advance!


#27968 Feb 16, 2009 11:30
  • Member since: 2002

    Check out this: 

    Go to IIS ->properties on your web site -> Home Directory -> Configuration...

     Press the Edit... button under "Wildcard application maps" and make sure that the "Verify that file exists" is NOT checked for your aspnet_isapi.dll file.

    Lars Øyvind 

    #27999 Feb 17, 2009 9:40
  • Member since: 2009

    Hi Lars Øyvind!

    Thanks for the reply!

    The problem is that the error occurs during the install so I haven't even got a web site installed on my IIS. I thought the creation of a web site in IIS was supposed to be taken care of by the EPiServer installer?

    /Thomas Kahn

    #28040 Feb 18, 2009 9:00

    If you install IIS after .net mapping will not be done properly.

    1. go to cmd

    1. go to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727(  if you have installed 2.0, otherwise go to the particular version folder)

    3. Type aspnet_regiis.exe

    It will start installing the regiis and maaping will be taken care by itself.

    Hope this will be useful

    Lakshmi Narayanan


    #28054 Feb 18, 2009 15:17
  • Member since: 2006


     We got this error here for the heinous crime of having the pre-SP1 version of the .NET Framework installed.

    If, in %WINDIR%\Microsoft.NET\Framework\ you have two directories: v2.0.50215  and v2.0.50727 then the R2 installer will bomb out with this error.

    To stop it, simply temporarily move the v2.0.50215 directory outside of the Framework directory (dump in on the desktop or something), run the installer, and then put it back before anyone else relying on it realized it was your fault their app stopped working :)

     Hope this helps!



    #28233 Feb 26, 2009 12:45