As you will see elsewhere on my blog, I have recently setup windows 2008 server 64bit as my new desktop. For the most part everything has worked ok, but there have been a few interesting quirks.

One of these quirks was that any new site I setup in IIS7 resulted in a "500 internal server error" identifying the AboMapperCustom wildcard application mapping for ColdFusion as the cause.

Now my Default Web Site from where I run the CFADMIN was working fine, so I was rather perplexed as to why other sites did not work when they seemed to be setup exactly the same.

Now I am actually using DotNotPanel on my local machine to setup and manage sites, so this may be a contributing factor, but still the cause of the problems may affect others, so hopefully the solutions may help.

Using the Web Server Configuration Tool I tried to disable then enable CFML on the server several times to no avail, then when checking the Handler Mappings" for the site, I noticed that the wildcard application map for CF was actually there twice, which I am sure may well have been a contributing factor, so I removed one of them. I also then noticed this alert on the handler mappings page.

This site is in an application pool that is running in classic mode, 
so you can manage ISAPI extension and native modules that are mapped to 
paths. You must manage managed handlers (system.web/httphandlers) directly 
in the configuration files.

Now if I recall "classic mode" means 32bit, so this seemed likely to be causing a problem, although I am not sure how I ended up using this application pool by default.

Anyway to change this, open the IIS manager, find your site, right click and select

Manage Web –> Advanced Settings

And change the application pool at the top to "Default Application Pool". In my case this fixed the problem and the alert went away, hopefully this may help someone else having issues with IIS7 and CF.

Views: 4232