OK, Mike. This explains why things are not working for you. (And thanks for your kind regards.)
You’re saying that you had CF9 (which had been working on Windows 7 with Apache), that you are now trying to run with Windows 10 and IIS. Can you confirm if the installer you’re using is an old one, like from several years ago? If so, that it likely installing 9.0, which did NOT support IIS 7 (which is what Windows 7/2008 added, and 8/2012 ran IIS 8 and 10 runs IIS 10). Now, you may find blog posts and resources where people showed how to hack 9.0 to get it to work with IIS 7 (just like now, there is this new post on hacking it, if needed, to get it to run with Windows 10/IIS 10). But Adobe DID address this problem of CF 9 not running with IIS 7, in their update 9.0.1. But to be clear, that is an updater to 9.0. If you are installing an old 9.0 installer, that is NOT 9.0 out of the box. You have to install it, and NOT integrate with IIS, and THEN install 9.0.1 over that, which then WOULD work with IIS 7. Or, note that in 2012, when CF10 came out, Adobe released yet another CF9 edition, called 9.0.2. That was a complete installer for 9 (not an updater, like 9.0.1). The main purpose of that release was to remove the Verity search engine (because CF10 removed, it, they had to—by license from Verity--also create a new installer for 9 that did not have Verity). That’s what 9.0.2 was. But it also incorporated, of course, all that had been in 9.0 and 9.0.1, which added the IIS 7 support. So bottom line, if you were to go get the latest installer for 9 (again, 9.0.2), then THAT would work with IIS 7 out of the box. (But again, 9.0.2 is a complete installer. You’d need to uninstall your 9.0 to proceed. Sadly, you can’t look at the installer file names to be able to tell whether it’s 9.0.0 or 9.0.2. That’s why I asked how long ago you’d gotten the installer you’re using. If you copied it from a machine where you had had CF9 running for years, then it’s likely 9.0, and THAT’s your problem. You need to get 9.0.2 (or add 9.0.1 to your 9.0), and THEN when it gets to the last step of the installer it SHOULD have no problem accessing IIS 7 (or IIS 10, in the case of Windows 10). And if you find later for some reason that you need to run that web server config tool, note that for IIS7 and above, you need to be sure to right-click on the tool (the web server config tool) and choose “run as administrator”. It’s just about increased security on Windows Vista and above. Finally, you may ask “how do I get this magical 9.0.2 installer? because Adobe no longer lists installers for CF9”. And that’s correct. Instead, one can get it via bit.ly/cfdownloads, a site created by Gavin Pickin and supported by myself and others to hold old installers for CF (from 11 down to CF4), and updaters, and hotfixes, and docs, and more. So Mike, let us know if you DID already get what you know is a 902 installer, and if you did not, go get it and try that, and let’s see if it all works for you. It would all make sense, if it did. I have a few blog posts I can share addressing the various things above, but in the interest of time I’ll hold off finding and sharing them until someone asks. /charlie From: cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] On Behalf Of Mike K Sent: Saturday, August 08, 2015 10:55 PM To: cfaussie Subject: Re: [cfaussie] CF and Windows 10 and IIS Charlie, I'm grateful to you for your willingness to step up, as always. You've been an asset to the community for a long time, and so it continues. All i wanted to do, was upgrade my windows. I have 4 machines all running Windows 7 (one with Win7 ultimate, 2 with Win7 Pro, and 1 with WIn7Home Premium. ) Being cautious ever since an awful experience with Windows95 years ago, I started with my WIn7Home Premium laptop, which I dont use very often. If it went pear-shaped on that machine it wouldn't be a big deal. And i can take as long as I need to get it worked out before I need to upgrade all the other machines. So I upgraded the Windows on that laptop. Went swimmingly. Just as advertised. Took me a couple of hours to get a human to talk to me at Microsoft so I could find out how to get hold of the installer so I didnt have to download it all 4 times, but finally i got what I needed. I upgraded my windows and started testing all the applications I had loaded on there. To my surprise everything worked. Just as they had previously, but with a better look. And to my amazement, the new Microsoft browser looks at first glance to be a fine piece of work. (But I have yet to give it a real good workout) And Bing is no better than it used to be. But when I went to check how my dev versions of my sites ran, I came into problems. They are built on CF9 Enterprise. My Apache didnt run. Wouldn't start. I could have debugged it and got it working maybe, but I figured that I didnt know enough about IIS, and I own a server that serves pages with IIS, and i really need to know more about IIS. So. why not take this opportunity to start using IIS in my dev environment. How hard can it be??? So I just left Apache alone. I removed it from the list of programs that auto start on reboot and that's where it stayed. HAH!!!! You'd think I would learn wouldnt you. These things NEVER run smoothly for me. Never have, so why would I expect this to be any different? I installed the IIS components, taking a guess as to what elements I'd be needing if all i was doing was using it as a web server for my ColdFusion sites and maybe a simple static site or two. I loaded a static site into it and it worked fine. Great. I can assume IIS is working ok, even if I'm not 100% i have all the required components. Now all I have to do is connect my CF9 to IIS and run a CF site on it and I can relax. If only! So if you've followed this thread you'll see that I started out just trying to add IIS using the Web Connector tool. That didnt work. It just hung, and never got to the point of offering me the web servers it's found for me to select. The dialog box opened and it started searching for web servers installed on the machine and that's where it stayed. So i figured maybe what I'll do is uninstall CF9 and reinstall it. That way I can eliminate Apache from everything, in case that was the problem. I did that 3 times all with the same result. I installed CF9 as each of the variants offered in the install routine. Each time it would install apparently fine, but hang at the last point where it's connecting to the web server. That's where I'm up to. I don't know whether a Windows10/CF9 combination is EVER going to work, or I need to go to a later version of CF. (I am sticking with CF9 because that's what 's on my server, and I like to have my dev environment as similar to the production environment as I can get. But I can upgrade if that's the only way to go to Win10. I guess I'm going to have to update CF sooner or later, but I have no need yet because of clients needing the newer features or anything like that. I dont want to go to that expense just to stay near the cutting edge. I'll upgrade when/if there's a client need. ) I want to upgrade all my machines to Windows10 for reasons unrelated to web development. There are some problems with another app that we use for the radio station programming that are unstable and need upgrading. It's not urgent but we have a year before Win10 is no longer free. So I dont know what to do next. I suspect one option might be "just wait till Adobe provide a fix." Do you have any suggestions? Cheers Mike Kear -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To unsubscribe from this group and stop receiving emails from it, send an email to cfaussie+unsubscr...@googlegroups.com. To post to this group, send email to cfaussie@googlegroups.com. Visit this group at http://groups.google.com/group/cfaussie. For more options, visit https://groups.google.com/d/optout.
