December 29, 2023
CF2023 failing when using IIS
Comments
(1)
December 29, 2023
CF2023 failing when using IIS
Newbie 2 posts
Followers: 1 people
(1)

I have just installed CF2023 developer on a new Windows 11 Pro system. I went through the steps to install the isapi handlers just as I’ve done in the past, and as far as I can tell, the installations went well.  CF applications are running fine when invoked using the CF built-in server (localhost:8500), but fail with a 500.0 status when using IIS. I tried installing IIS’s “failed request tracking”, but although the 500 error is logged in the IIS logs, nothing is logged in the failed request logs.  This sounds like an IIS install issue, rather than CF, but I have no idea what to check/reinstall/correct.  Any suggestions would be welcomed.

1 Comment
2024-01-01 14:59:54
2024-01-01 14:59:54

First, have you confirmed that the 500 error that iis shows isn’t a cf error (whether due to code or config), that may be logged in cf’s logs? Check first the application.log, the exception.log, the coldfusion-out.log, and/or the coldfusion-error.log.  Such errors would not show up in iis or frt. (BTW, when you say “nothing” is logged in the frt logs, do you mean no info on this error? Or no frt log for the request at all? The latter could have many different explanation–having nothing to do with CF.)

If the CF logs show nothing, please confirm if you are running the same code in the test of iis vs cf. You can also try creating a new folder in the iis web root, with a blank application.cfc (or cfm) and a blank test.cfm or with minimal cfml. Does THAT run without an error? If so, it confirms the error was in your code or the application.cfc/cfm it was implicitly running.

Finally, what’s your reasoning for manually configuring things? Why not use the cf wsconfig tool? Indeed, there is more than just adding “isapi handlers”: there are handler mappings, an isapi filter, and a jakarta virtual directory, and all those should point to a folder (typically a numbered one within cf’s config/wsconfig directory). The wsconfig tool does all this.

And the tool knows to point a key entry in the workers.propertires file at a port configured in the server.xml file in cf’s cfusion/runtime/conf.

When you do all this manually, you open yourself to making any of many possible mistakes. Thus my question.

Indeed, if you may have “just copied” the config folder from some previous cf version, that wouldn’t work typically.

If none of the above helps, there are potentially many remaining possible explanations for your error. This is already long enough. Let us know if any of these help or not.

Like
(1)
Add Comment