Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

In my IIS7 configuration there appears to be a few handlers of the following form:

  • name: AboMapperCustom-[number]
  • path: *
  • preCondition: [empty]
  • scriptProcessor: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll

What is this for? Looking around MSDN suggests that ABO may be Admin Base Objects, but there's nothing obvious as to why that would need this kind of handler.

I think it's causing some issues for aspnet 4.0 applications on the machine due to the blank preCondition. I'm looking into 'fixing' the issue, but I'd like to know why the handler was created and what it's intended to do.

Thanks!

share|improve this question
add comment

migrated from stackoverflow.com Aug 22 '11 at 14:07

This question came from our site for professional and enthusiast programmers.

1 Answer

AboCustomMapper handlers are there to provide legacy support for applications that create mappings on IIS7 via the IIS6 compatibility layer (ADSI) instead of using the new managed API. i.e. the code creates IIS6 metabase Script Map objects which the IIS6 compatibility layer translates to handler mapping objects. They get named AboCustomMapper-XXXXXX because there is no equivalent name property in IIS6 for a script map, this is an auto-generated name.

ADSI on IIS7 is ignorant of Handler Mapping (analogous to an IIS6 Script Map) properties such as preConditions which, for example, permit multiple versions of ASP.NET's handler mapping definitions to co-reside in the same site or application. The ADSI compatibility layer will create objects known as AboMapperCustom objects which are sub-optimal in their configuration and are not aware of these new features.

In your case it looks like something (code/installer?) has created the equivalent of an IIS6 wild card script map to map any and all requests to ASP.NET and it has done this via the IIS6 compatibility layer.

This kind of thing isn't really needed any more on IIS7 with IIS7's integrated pipeline mode. You could edit the handler mapping and set the path to something like *.disabled to push it out of the way and then see what side effects or improvements that causes.

share|improve this answer
1  
+1 In IIS 7 Manager > [your site] > Handler Mappings you can remove all the AboMapperCustom-##### handlers. This will add a bunch of <remove name="AboMapperCustom-#####" /> entries to your Web.config (worked for me). I guess it could have been created by cold fusion or something similar. –  Myster Oct 29 '12 at 2:42
    
isapi_wsgi for python creates AboCustomMapper-xxx handlers too. –  solublefish Jul 14 '13 at 0:46
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.