Today we had to install 64bit CF9 on Windows Server 2008 64bit running IIS 7.
Even though the installation ran just fine, IIS was not configured with the correct ISAPI mappings to server CFM files. In fact it looks like it was not configured at all!
I then decided to run the
C:\ColdFusion9\runtime\bin\wsconfig.exe tool that ships with CF9 thinking that would do the trick. It didn’t work, first giving an error that it was:
Enabling IIS7 optional packages.... it will take 2 to 5 minutes...
Then when I tried to add the config again it told me:
Error creating IIS application extentions * from web site All(0)
The solution is to add the mappings yourself. However, the
wsconfig tool did do an important step: It added the following dir:
You’ll need that later.
Going from a web server (32 bit) on which CF9 did install correctly I added the following to IIS7 at the server (not site!) level:
ISAPI and CGI Restrictions
- C:\ColdFusion9\runtime\lib\wsconfig\1\jrun_iis6_wildcard.dll (Description: Macromedia Server Extensions)
- C:\ColdFusion9\runtime\lib\wsconfig\jrun_iis6.dll (Description: Macromedia Server Extensions)
Handler Mappings (add these a Script Maps!)
- *.cfm to C:\ColdFusion9\runtime\lib\wsconfig\jrun_iis6.dll – CF Mapping CFM
- *.cfml to C:\ColdFusion9\runtime\lib\wsconfig\jrun_iis6.dll – CF Mapping CFML
- *.cfc to C:\ColdFusion9\runtime\lib\wsconfig\jrun_iis6.dll – CF Mapping CFC
- * to C:\ColdFusion9\runtime\lib\wsconfig\1\jrun_iis6_wildcard.dll – CF Mapping Wildcard [note: this was added by
Restart IIS and you should be able to serve your ColdFusion pages again.