Jan
27
by Mike Fleming at 7:00 am (3 Comments) ColdFusion, Windows
Late last week I spent a day trying to install ColdFusion 8 Enterprise on a new 64 bit Windows Server 2008 server. It did not go well at first. The install itself succeeded, but nothing was working. When trying to launch the administrator to complete the installation, IIS threw one of the most bizarre error messages I have seen. After doing a little research the error was trying to tell me that it was having a problem using the ISAPI filter for ColdFusion. This was due to the fact it was made for IIS 6. If you have ever noticed, the .dll that parses the ColdFusion requests is named jrun_iis6.dll.
I then came across a blog entry from Jason Holden describing exactly what needed to be done to get everything working. I uninstalled ColdFusion, and followed the steps from the blog entry. I then reinstalled ColdFusion and everything was working normally. In short, IIS 7 must be set up to handle filters made for IIS 6. The only question I have is why hasn't Adobe addressed this in the installation notes? It sure would have saved me some time! And kudos to Jason for the tips.
Paul Kukiel
January 31, 20094:08 pm
This is really frustrating its the same on Vista with IIS7 and Windows 7. Before I knew the workaround I did a heap of manual hacking to get it to work. You are right though Adobe really should address this as I see people constantly asking how to get CF going of IIS7.
Daryl Banttari
January 31, 20094:36 pm
It’s actually pretty easy– use the 64bit installer to set up the connector, then use the 32-bit version of ColdFusion with it.
http://cfprimer.blogspot.com/2009/01/coldfusion-8-professional-with-windows.html
token
March 26, 200910:45 am
Thanks a lot for this post. I found it through Google after struggling with installing CF8 32bit on Server 2008 64bit. I must have installed/uninstalled at least 8 times before finding this.
Thank you!