Since you upgraded, is it just that the service name in Windows still says "9"?
Do you have 2 windows services; one for 9 and one for 10?
Yes, two Application Server services, one for 9 and one for 10.
Was that your intention? I mean, did you want to run 9 and 10 or did you want to upgrade 9 to 10 (replacing 9)?
Intent was to install 10 and remove 9. Problem turned out to be version 9 still had its hooks in IIS until I removed the reference via configuration manager. All is well now. Thanks for your interest Miguel.
Correct, you want to always make sure all ISAPI modules, handler mappings, and CGI filters are removed.
Question though -- we are running into this same issue with the CF 10 upgrade to CF 9. Is the installer supposed to remove these, or is it the case that you are supposed to go in and remove manually?
Best Practise is first remove the connector from your previous server(using WSCONFIG utility) which is ColdFusion 9 in this scenario, and then check IIS manager if any thing left for ColdFusion 9 which is redirecting it there, if you find anything there remove it manually.
And then install ColdFusion 10 and create the connector, because if there are any left over of previous server you will face this issue.
Installer of ColdFusion 10 will not remove these setting when you upgrade from ColdFusion 9 to CF 10.