CF11 is not supported on Windows 10. Having said that perhaps you would like to try the pre-release updater 7 for use with IIS on Windows 10:
Looks like the connectors have not been configured properly.
Please follow the below blog to get the supported wsconfig, and re-add the connectors.
I'm having the same problem. Will report back if I find a resolution. Stating "windows 10 is not supported" doesn't seem like a valid answer, it's just an operating system running Java and IIS, so not sure how that could possibly be correlated in that way.
There is an answer, and we haven't found it yet.
Will attempt and post back if confirmed functional.
bdeg, this problem has been solved, long ago (late 2015, with CF11 update 7).
You must have missed it at the top of the reference you made to the blog post (which was from before the original post above). It points now to the post that came out just after that, where the update was finally released:
So bottom line: yes, CF11 supports Windows 10 since that update.
This ticket is still marked as unanswered since in order to actually utilize the referenced article, which wasn't mentioned anywhere in this thread until I myself mentioned it, you would need to have the Coldfusion update installed somewhere. Which you can't upgrade unless you can access CFIDE, and you can't on windows 10 (more importantly, IIS 10) -- hence this thread.
So I don't think I missed much, let me know where I'm wrong on that. The ordering of dates of postings seems irrelevant when one is coming from a google search attempting to find an answer to an unanswered question, is it not? Surely more information is better than less.
I think the only thing that irks me more than an unanswered thread which certainly could've been answered, is someone (especially of your caliber) trying to bash another for sharing information on said lack of information. What a shame.
For me, the resolution was to install coldfusion using the integrated web server. Upgrade via CFIDE (it installs latest, you need update 7. The latest update apparently doesn't include this super useful update. I had to post-re--update to latest AFTER explicitly installing update #7 followed immediately by running IIS configuration via wsconfig tool), shutdown services to disable built-in server via server conf(optional), then iisreset.
For me, Doing as the article described (copying wsconfig.jar from a working upgraded machine, extracting, reconfiguring) did not resolve the problem, despite following the article exactly (and then some... manual config tried as well)
Curious how a little effort can go so far, even from a small-time cfusion user like myself. Further, how nice it must be to be the next person to happen across this, and have a valid answer present and typed explicitly.
Here's a screenshot for proof in case you had any additional doubts in my aptitude, eyesight, comprehension of dates, or reliability of resolution:
See you on the next unresolved article! Thank you for your super helpful response!
I'll mark your answer as correct. Thanks for the lesson.