Skip to: Site menu | Main content

Email LinkedIn

Blog...

IIS 7/8 and Coldfusion 10

While deploying my first Coldfusion 10 server on Windows 2008 R2 SP1, I ran into this strange behavior.

My IIS Default website had no issues processing CFM files after the install. However other IIS sites would not process any CFM pages. The message I received from IIS was the standard 404.

Accessing the URL on the server I found that the requested URL was: http://{my site}/jakarta/isapi_redirect.dll

Just to see if it would work I mapped a virtual directory named "jakarta" to


CFUSION INSTALL\config\wsconfig\{instance id}

Magically my site began processing CFM files.

Sami Hoda's entry pointed me in the right direction of running the WSConfig utility on each instance.

The WSconfig more completely configures the site, but still seems like a pain to have to do this on every new site.

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)