CF and Windows 10 and IIS
Mike K
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
ColdFusion 9 Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month
Rae Buerckner
Why not just upgrade and see how Apache goes, I’ve been using it no probs J
Cheers,
RAe
Rae Buerckner
ACT Adobe Product User Group Manager
--
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+u...@googlegroups.com.
To post to this group, send email to cfau...@googlegroups.com.
Visit this group at http://groups.google.com/group/cfaussie.
For more options, visit https://groups.google.com/d/optout.
Mike K
Rae Buerckner
Sent from my iPhone
Mike K
And I'm sure you had the normal result from Apache but I've never had the normal result from Apache ever since I first started using it back at CF5 days. It's always been a pain in the neck to get it to do anything on a new install. The only thing that works fine for me with Apache is installing a new web site.
Anyway I now have servers on line with IIS and I need to know a lot more about managing them than I do, so that's the main reason I wanted to switch. This hiccup with Apache now is not unexpected, given the history I've had with it, but it's given me the push to get off my ass and learn more about IIS.
Rae Buerckner
Sent from my iPhone
Rae Buerckner
Just an aside, did you follow the ACME guide for installing CF with Apache? If not that may be the root of your problems J
Cheers,
Rae
Mike K
Me: I have a problem installing this
Community: well I didn't
Me: well I do and I'd be grateful for a hint what I can do to find out what I've done wrong
Community: Well it worked just fine for me
Me: good I'm pleased for you. But any idea how I figure out what's different in my case so I can work out a way around it?
Community: it works fine for us. Must be you.
In other words. Not much help on installation issues Oh and none at all ever from adobe or any of their predecessors
Cheers,
Mike Kear
Mike K
[ A ] Run the jrun web server configuration utility. ( the green thing ) to connect ColdFusion to IIS It hangs saying it can't find a folder. But doesn't tell me which folder it can't find and since there's no place to enter a folder location up to that point I have no way to find out.
[ B ] uninstall ColdFusion, thinking if I reinstall it, it might resolve that folder issue by itself. Nope. Still hangs at the point of configuring the web server. Obviously the same problem, but still no way to work out what the problem is
[ C ] uninstall ColdFusion again and reinstall as single server rather than J2EE. Same result
So unless I can get the web server configuration utility to work I think I'm screwed on this machine
Cheers,
Mike Kear
Ricardo Russon
Peter Tilbrook
Professional Adobe ColdFusion 11 Application Development
Managing Director, ColdGen Internet Solutions
PO Box 2247
Queanbeyan, NSW, 2620
AUSTRALIA
Tel: +61-2-6104-9981
Mob: +61-0478-623-579
Email Address: peter.t...@coldgen.com
WWW: http://www.coldgen.com/
Mike K
And thanks Ricardo I'll give your suggestion a try too
Cheers,
Mike Kear
Peter Tilbrook
Professional Adobe ColdFusion 11 Application Development
Managing Director, ColdGen Internet Solutions
PO Box 2247
Queanbeyan, NSW, 2620
AUSTRALIA
Tel: +61-2-6104-9981
Mob: +61-0478-623-579
Email Address: peter.t...@coldgen.com
WWW: http://www.coldgen.com/
Charlie Arehart
Peter, you mean *CF12* is in prerelease (not CF11, which has been out for over a year). And Peter you say “no joy getting CF10 to work with Win10”. What problem have you had? I upgraded a dev machine running CF11 (with IIS) to Windows 10, and I have seen no problem.
Mike, as for your efforts, you don’t say what version of CF you’re installing (only that you’re doing it on Windows 10, which to be clear is not formally supported yet by Adobe). I assume it’s CF10 or 11, since you refer to moving from CF9.
Here’s a more pressing question: are you trying to install CF10 or 11 on the same machine that was running CF9? If so, and if it had been running CF with IIS, you would face challenges if you didn’t first remove the web server connector for IIS. But since you say you were using Apache, you may want to do that also (running the CF9 web server config tool).
You also don’t say what the version of Windows (and IIS) was that you are moving from. It might be significant. Was it Windows 2003? Windows 7 or 2008? Windows 8 or 2012? Again, it could be significant to know if you are moving from one machine to another, or upgrading a machine in place (where CF had run before).
Now, you say later that you tried it and had problems. When you say you ran the web server config tool, is this after you had upgraded CF, or before? You refer to it as the “jrun” tool, so it sounds like the CF9 one. Was that in the hopes of removing the old connector? Do you still have CF9 installed? And running? If not, that could be why it’s hanging up.
Then you talk about uninstalling/reinstalling CF. Again, was that 9 or 10/11?
If time is of the essence and you don’t want to wait for back and forth (across timezones and datelines), I’ll note that if you wanted to have some direct help resolving this (remotely), I could help. See the consulting page at carehart.org for more info on rates, approach (no need to open firewall or grant me an account on your server), satisfaction guarantee, and more.
Now, to folks who may get cranky at that “sales pitch”, please note that I have first offered AMPLE and substantive info above to try to help Mike here for free. I only point out the other option if it may be helpful for him, or anyone who finds themselves in a jam with a CF server troubleshooting problem. That’s all I do, all day, as an independent consultant, serving several different folks each week. But I do love to help for free on lists like this, forums, and so on, when I can.
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Peter Tilbrook
Sent: Saturday, August 08, 2015 8:11 AM
To: cfau...@googlegroups.com
Subject: Re: [cfaussie] CF and Windows 10 and IIS
Have not tried this yet but hope it helps as so far no joy getting CF10 to work with Win10. Have not tried CF11 as that is still alpha.
What if you run the "Remove All Connectors" script before running the config tool?
On Sat, Aug 8, 2015 at 7:13 PM, Mike K <afpwe...@gmail.com> wrote:
In this case I have now tried :
[ A ] Run the jrun web server configuration utility. ( the green thing ) to connect ColdFusion to IIS It hangs saying it can't find a folder. But doesn't tell me which folder it can't find and since there's no place to enter a folder location up to that point I have no way to find out.
[ B ] uninstall ColdFusion, thinking if I reinstall it, it might resolve that folder issue by itself. Nope. Still hangs at the point of configuring the web server. Obviously the same problem, but still no way to work out what the problem is
[ C ] uninstall ColdFusion again and reinstall as single server rather than J2EE. Same result
So unless I can get the web server configuration utility to work I think I'm screwed on this machine
Cheers,
Mike Kear
<snip>
Mike K
Andrew Scott
Andrew Scott
Mike K
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
Andrew Scott
Mike K
Mike Kear
Paul Kukiel
--
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+u...@googlegroups.com.
To post to this group, send email to cfau...@googlegroups.com.
Visit this group at http://groups.google.com/group/cfaussie.
For more options, visit https://groups.google.com/d/optout.
Charlie Arehart
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: cfau...@googlegroups.com [mailto:cfau...@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.
Charlie Arehart
Woah, woah. Slow your roll, Mike. :-) To you both, about CF not supporting Windows 10, well I did point that out in my last note. It is NOT yet supported.
And if you visit the Adobe blog post (which Peter pointed to), there’s a discussion of that (which I initiated last night). The post is http://blogs.coldfusion.com/post.cfm/configuring-connectors-manually-for-iis-10) where they offer the steps for how to get an aspect of CF 10/11 to work with IIS on Windows 10 (which I did NOT need to do to get CF 11 running ok on Windows 10). And those interested will see there that I offered a comment there for Adobe asking (as I knew many would) when CF 10/11 would be updated to run on Windows 10? And I address the countervailing points of “well no one should run a new OS in production as soon as it comes out” vs “but developers need to be able to test against it as soon as it comes out”. We’ll see what they may say.
And Mike, you ask here “does this mean NO ONE is using ColdFusion and Windows 10”, I said in my last post that I DO have it working myself ( but again, it’s not supported yet.)
Moving back to your problem, I hope my earlier not (just sent) helps with that. It’s 11pm my time, so I probably won’t see a reply until my tomorrow.
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Mike K
Sent: Sunday, August 09, 2015 10:35 AM
To: cfaussie
Subject: Re: [cfaussie] CF and Windows 10 and IIS
So does this mean NO ONE is using ColdFusion and Windows10?? I do hope Adobe have this issue fairly high on their list of things to fix.
--
Mike K
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
Mike K
The link to the repo Charlie gave me has DOZENS of folders containing DOZENS of versions of ColdFusion and documentation and CFBuilders and all that. And one of the folders is empty. Only one. Guess which one?
Mike K
Andrew Myers
Andrew Myers
Oops that's the same one Charlie already shared. Sorry :)
Charlie Arehart
Mike, that’s very interesting. As I visit it now, it has all the installers. I think sometimes that copy.com interface (which underlies the current repo that Gavin has used for months) is quirky and sometimes shows blank when it’s just being slow to respond. To be clear, I am viewing the downloads right now for 902. Here’s the link:
https://www.copy.com/s/t%3AnhIbHZYZnmPN%3Bp%3A%252FColdFusion%2520Repo/9.0.2%3Boid%3A381
I confirmed this worked on another browser in another machine, so it seems a portable/shareable link. One thing: it took about 12 seconds to come up on that other machine, to show the files. Gavin is aware that the copy.com service is not working well and he’s contemplating a new location for the repo. But that bit/ly/cfdownloads link should always take you to the page he uses to point to the repo, wherever it may end up.
Let us know if that gets you going,
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Mike K
Sent: Monday, August 10, 2015 12:24 AM
To: cfaussie
Subject: Re: [cfaussie] CF and Windows 10 and IIS
Figures. This is the story of my life.
The link to the repo Charlie gave me has DOZENS of folders containing DOZENS of versions of ColdFusion and documentation and CFBuilders and all that. And one of the folders is empty. Only one. Guess which one?
Charlie Arehart
Thanks for the update and the kind regards, Mike.
One thing: you say you’ll “download the CF9 updater” because “removal of Verity doesn’t affect you”, but I want to make clear again that 902 is NOT AN UPDATER. You will need to uninstall your 9.0 or 9.0.1 install before proceeding. More on it at http://www.carehart.org/blog/client/index.cfm/2013/8/19/understanding_ColdFusion_9.0.2_a_FAQ. Just want to be clear on what it is, and is not.
Indeed, as for my thinking ahead to provide that download repo link you needed, I’ll just note that there’s a fine line between my “reading folks minds” in offering such extra detail, and being counted a “tall poppy”, but it’s a line I feel I need to walk. :-)
I saw your next note where you had trouble getting it at the download repo. Will reply to that separately.
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Mike K
Sent: Monday, August 10, 2015 12:15 AM
To: cfaussie
Subject: Re: [cfaussie] CF and Windows 10 and IIS
Charlie, I think you've put your finger right on the issue. I dont know for sure till i go check, but I'll bet I havent updated my CF9 that far, certainly not on this laptop that I rarely use. I'll do that and see if that fixes the problem.
Mike K
I downloaded the CF9.0.2 from the repo that Charlie sent me to. It was in a folder that was blank when I looked at, and blank again when I looked at it again, while other folders had content in them. But when Andrew sent me back there ... lo and behold! There was content. So I downloaded the file. So far so good.
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
Andrew Scott
--
Paul Kukiel
Mike K
Andrew Myers
Not sure if it's a path you would consider but I had a situation where I needed to run Cf11 on Red Hat 5.x which is not a supported platform. Upgrading the server wasn't an option at that point in time.
My solution was to create a war file from the installer (can be done on another machine) and deploy it on Tomcat on the Rh server. I then uses mod-jk to hook it into the Apache version (the older Apache version was the actual problem with the Adobe connectors).
Given you're on IIS I don't know how you'd connect tomcat but I expect being such a widely used app server there'd be doco on it.
You do it at your own risk though, it's an unsupported platform after all. But I'm willing to share what I did on the tomcat side of things if it's any help.
Andrew Scott
Mike K
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
Charlie Arehart
Mike, I’m catching up on the past several messages from my overnight. So bummer about what’s happened. (And let me be clear: I had only said I had run my CF11 on Windows 10, not CF9. The rest of my earlier thoughts were focused on why CF9.0 would not work by default with IIS7.)
So as for your challenge, one of Andrew’s ideas is interesting, about having Win7 first, to do the install of CF9, and THEN upgrading Windows. But that’s a hassle, of course, as you have already upgraded Windows. And using VM’s is certainly another way to go, but again may be overkill for your immediate need.
So back to the root cause problem, Andrew and Paul propose that it could be that CF9 would not install on Windows 8, let alone 10. I’d think if that was so, we’d have heard about that from others for the past couple of years, but I have not (but it may be I have just missed the news).
I wonder if there may be something else about your setup that’s unique. I can’t think of an alternative off the top of my head. I’d like to try running that 902 installer on my own Win 8.1 (and 10) setup, but can’t do that for another couple of hours. If anyone else shares any experience/confirmation (past or present), it could be interesting to hear.
I’m just not so ready to give up on your hope yet. :-)
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Mike K
Sent: Tuesday, August 11, 2015 8:44 AM
To: cfaussie
Subject: Re: [cfaussie] CF and Windows 10 and IIS
Andrew (Scott) thanks for your input. Incisive as always.
Andrew Scott
Mike, I’m catching up on the past several messages from my overnight. So bummer about what’s happened. (And let me be clear: I had only said I had run my CF11 on Windows 10, not CF9. The rest of my earlier thoughts were focused on why CF9.0 would not work by default with IIS7.)
So as for your challenge, one of Andrew’s ideas is interesting, about having Win7 first, to do the install of CF9, and THEN upgrading Windows. But that’s a hassle, of course, as you have already upgraded Windows. And using VM’s is certainly another way to go, but again may be overkill for your immediate need.
So back to the root cause problem, Andrew and Paul propose that it could be that CF9 would not install on Windows 8, let alone 10. I’d think if that was so, we’d have heard about that from others for the past couple of years, but I have not (but it may be I have just missed the news).
I wonder if there may be something else about your setup that’s unique. I can’t think of an alternative off the top of my head. I’d like to try running that 902 installer on my own Win 8.1 (and 10) setup, but can’t do that for another couple of hours. If anyone else shares any experience/confirmation (past or present), it could be interesting to hear.
I’m just not so ready to give up on your hope yet. :-)
/Charlie
Andrew Scott
Charlie Arehart
Well, no, I did not. There are couple points to consider (for any interested in his question and my answer).
First, note that I had said that mine was a machine that was already running CF11, on Windows 8.1, which I upgraded to Windows 10. I was only saying (all along) that it’s definitely not that CF10 “can’t run on Windows 10”, as some were saying (perhaps just being lose with what they meant).
Second, there may well be issues either with the connectors, for some people, which I acknowledged the first day, saying:
“And if you visit the Adobe blog post (which Peter pointed to), there’s a discussion of that (which I initiated last night). The post is http://blogs.coldfusion.com/post.cfm/configuring-connectors-manually-for-iis-10) where they offer the steps for how to get an aspect of CF 10/11 to work with IIS on Windows 10 (which I did NOT need to do to get CF 11 running ok on Windows 10).”
Third, andn to that, someone may say, “ok, but that’s only if you have things configured BEFORE you update to Windows 10. You can’t update the connectors once RUNNING Windows 10, can you?”
Well the answer (just tested) is “yes I can”. That also is why I said, in other notes in this thread, that while that Adobe forum post seems to be needed for SOME people running on Windows 10, it was not needed for me.
So fourth, maybe there is something where if you INSTALL CF10 or 11 on Windows 10 and THEN try to run the wsconfig tool, some may have a problem. Again, I already had CF11 installed when I updated from Windows 8.1 to Windows 11.
HTH.
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Andrew Scott
Sent: Tuesday, August 11, 2015 1:02 PM
To: cfau...@googlegroups.com
Subject: Re: [cfaussie] CF and Windows 10 and IIS
Charlie,
Charlie Arehart
Doh, I have to “call BS” on myself. :-( When I said below I had run the wsconfig tool to update the connector, and it had worked. I spoke too soon (before sending off the email, as I was right up against another call).
Curiously, while I was indeed able to REMOVE the existing connector (with the CF11 wsconfig tool, running as Admin, on Windows 10), and I was able to start the process of adding the connector back (still running as Admin), I should have waited just another moment before sending the email.
Like others, I’m sure, I got a popup from it saying that while it supported IIS 4, 5, 6, 7, and 8, it did not support 10. So the tool is checking the IIS version and deciding whether to proceed.
And that would then be why Adobe offered the blog entry (which Peter had pointed to) showing how to do it manually. And of course, one can do it manually, pretty easily. So to be clear, again, one CAN run CF11 (and I assume CF10) on Windows 10, and the IIS connector will work, as long as you don’t have to update it (remove/re-add it), as may be required in later CF updates. If you do need to update the connector, then you have to use the manual steps.
Now, this may seem to have gotten off-track from what Mike had originally raised: getting CF9 to run on Windows 10. The first challenge is getting the CF installer itself to work on Windows 10 (possible, but not trivial), then the second is getting the connector tool to work on it (not likely). You will likely find, Mike, that you’d get5 the same error I did, above. And while you can’t follow the exact steps Adobe offere3d in the blog post to get the connector working manually, you should be able to use it as a template, if you’re familiar with how the CF9 (and earlier) wsconfig tool edited IIS. Again, pretty easy to do. Someone ought to do a blog post about it at some point. ;-}
I’m working on more details for getting the CF9 installer to work on Windows 10. In the meantime, there’s a hack way that was also needed for CF9 to run even on Windows 8. I’ll share that in a follow-up note coming next.
/charlie
Charlie Arehart
OK, I had some time earlier to do some digging. First, I can confirm that I got the same error (offered by Mike with CF9 on Windows 10 when installing CF9 on Windows 8.1. So it’s not really new to 10. But there is an explanation, and a solution (one, though I hope to find another).
I found someone confirming this same problem in 2012, in a forum thread at https://forums.adobe.com/thread/1051315, and there someone offers a link to a blog post from someone else back then who (as I suspected) indicates that it’s about the JVM used by the installer. He suggests replacing the JRE within an extracted version of the CF installer (http://thefusionator.com/the-trifecta.html), and I have no doubt it would work but it seems obtuse. If there was a simpler solution, I’d love to find and share it.
Again, to be clear, all this indicates that the problem is not about CF, per se, but about the installer which it uses (InstallAnywhere), and specifically the version which was embedded with CF when they built these CF9 installers a few years ago. (Adobe DID update the installers for CF10 and 11, of course, to run on Windows 8.1, and if the pattern follows, they may come out with a new installer for 11 that supports Windows 10, and surely CF12 will.) And it’s not just happening to people on Windows 8 but also Server 2012 (which is basically the server version of Windows 8).
In the meantime, looking for more on this problem, we do indeed find many folks (who are not using CF but other apps, which use that older installer software) complaining of the same thing. As I look into such solutions, some have suggested things which did not work for me:
- Some suggest running the installer “as admin”, which Mike already said didn’t work for him. I got the same error as running without it.
- Some have suggested modifying the compatibility property for the installer (right-click, choose properties, then “compatibility”) to set it to Windows 7. I did that, but while it the installer starts, it never finishes. It just quietly goes away (the UI disappears, along with the listed process in task manager).
I do hope there may be some better way to solve this than the hack offered above, and I’ll keep looking, but in the meantime it may help you, Mike. (Just remember what I said in my last note just now, about your needing to do a manual update to the IIS connector.)
/charlie
--
Charlie Arehart
OK, here finally is what you can do, Mike (or anyone interested) to get things running.
I mentioned below that the “fusionator” blog post had talked about the process, and the key is that he suggests you extract the ColdFusion installer exe (yep, it is basically a zip, as an exe), and then he mentions “replacing the JRE” that comes with that with a more updated one (which does support Windows 8 or 10, such as Java 8 or perhaps later editions of Java 7). He doesn’t say anything more than that (about that process), so I assume he really meant “copy/paste” the JRE folder from an updated JVM to that folder in the extraction of the exe. (He also doesn’t give details about “what” JVM should be used. I will, below.)
While you can do that, you don’t really have to.
That same extracted folder (mine was C:\Users\charlie\Downloads\ColdFusion_9_WWEJ_win64\) will also have a \Windows folder, and in there will be a adobe_cf.lax, which is somewhat like CF’s jvm.config, as it’s a property file of JVM args for the installer. In that file, there will be a line:
lax.nl.current.vm=resource\\jre\\bin\\java.exe
This is what points the installer to the JVM that’s included with the installer itself (and it’s that JVM which doesn’t work on Windows 10 or 8.1). But my point is that you can just change that to point to an “updated” JRE\JVM path that you can obtain.
But here’s a catch: as I review that lax file, it seems clear that it expects a 32-bit JVM (even if the CF you are installing is 64-bit). Again, this is just about the JVM for the *INSTALLER*, and so it must bundle (inside that exe) a 32-bit jvm. So if we are going to point it at another, then we need that to be a 32-bit JVM.
I did it by pointing at a 32-bit Java 8 JDK that I got (at http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html). I could have gotten a JRE instead, but I tend to just always get JDKs. I really don’t think it matters in this case. But it HAS TO BE 32-bit, or the next steps will not work. When I installed that JDK, it installed to C:\Program Files (x86)\Java\jdk1.8.0_51, and THAT is where I needed to point the lax file (coming up). The “program files (x86) tells you that it was a 32-bit JVM. (Something that one may miss: when you’re running the installer for Java, there is a screen with various options you can choose, one of which is whether to install it as a “public jre”. There are good reasons to tend to favor NOT doing that, which is what I always do, and if you do that, then this path I point to is where it will be installed, by default.
So with that in place, I changed the line in the lax file to:
lax.nl.current.vm=C:\\Program Files (x86)\\Java\\jdk1.8.0_51\\bin\\java.exe
Note the use of double-slashes. This is just a necessary hassle with Java on Windows. (And while it could point to the jre\bin, within the JDK folder, it was not necessary.)
Finally, as “the fusionator” goes on to say in his post, you then do also want to right-click the installer exe (in that extracted folder), adobe_cf.exe, and enable windows 7 compatibility. (Otherwise, the installer will start but then complain that “installer user interface mode not supported”.) Then you run that adobe_cf.exe (not needing it to be run “as admin”, in my testing).
Once I did all this, the CF9 installer now did launch.
So no, my approach (of editing the lax file) is not necessarily fewer steps than “the fusionator”’s approach of “just copying/replacing the JRE folders”, but it seems a bit safer in case something goes amiss. It’s easier to undo and try again, which I needed to do for various reasons in getting this all working.
So Mike, there you go. With either what the fusionator shared (and my additional info about the “right” JVM to get), and copy/pasting over the JRE that comes with the installer, or with my tweak here to just edit the lax file to point to it elsewhere, you should be able to get the CF9 installer running on Windows 10.
Let us know how you get on, if you try it. (And again, let’s not lament, “why does Adobe make it so difficult?” Again, this CF9 installer was created in 2012, before Windows 10 came out. And they DID add support for Windows 8 in an update of CF10 and in CF11 out of the box. I’m sure we’ll see an update for CF11 to support Windows 10, and maybe CF10, and certainly CF12 will support it out of the box.) And before saying “Lucee or Railo don’t have this problem”, be sure you’re looking at an installer of theirs from 2012 or before, or it’s just not an apples-to-apples comparison.
HTH.
/charlie
Andrew Scott
rai...@ozemail.com.au
Hi Charlie
Thanks for your suggestion and reference material
Regrettably despite trying them I am still no further along
Is there a way I can simply re backup the original database making sure I select the correct options so that when I restore it on the new server the new server credentials are automatically applied ???
Claude
Charlie Arehart
Claude, I’m confused. This is your first time chiming into this thread (about CF and Windows 10), that I can see at least.
So are you saying that your database restore and SQL Server issues are on a Windows 10 machine?
I realize you wrote later that all was sorted, but I’m just curious whether you really meant to be asking your question in this thread (and you are trying to use CF on Windows 10) or that was just a slip?
Really looking forward to hearing Mike, if it may have helped him, or anyone else who may have been able to/interested in testing the solution I’d offered. I’d like to blog about it, after ensuring there’s nothing I’ve missed or left out here.
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of rai...@ozemail.com.au
Sent: Wednesday, August 12, 2015 6:13 AM
To: cfau...@googlegroups.com
Subject: RE: [cfaussie] CF and Windows 10 and IIS
Hi Charlie
Thanks for your suggestion and reference material
Regrettably despite trying them I am still no further along
Is there a way I can simply re backup the original database making sure I select the correct options so that when I restore it on the new server the new server credentials are automatically applied ???
Claude
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Charlie Arehart
Sent: Wednesday, 12 August 2015 5:10 PM
To: cfau...@googlegroups.com
Subject: RE: [cfaussie] CF and Windows 10 and IIS
OK, here finally is what you can do, Mike (or anyone interested) to get things running.
I mentioned below that the “fusionator” blog post had talked about the process, and the key is that he suggests you extract the ColdFusion installer exe (yep, it is basically a zip, as an exe), and then he mentions “replacing the JRE” that comes with that with a more updated one (which does support Windows 8 or 10, such as Java 8 or perhaps later editions of Java 7). He doesn’t say anything more than that (about that process), so I assume he really meant “copy/paste” the JRE folder from an updated JVM to that folder in the extraction of the exe. (He also doesn’t give details about “what” JVM should be used. I will, below.)
While you can do that, you don’t really have to.
That same extracted folder (mine was C:\Users\charlie\Downloads\ColdFusion_9_WWEJ_win64\) will also have a \Windows folder, and in there will be a adobe_cf.lax, which is somewhat like CF’s jvm.config, as it’s a property file of
<snip>
Charlie Arehart
Well, yes, I had set that yesterday. :-)
I didn’t think I needed to repeat it here, as it was the last sentence of the note which I responded to, with this later note being its follow up. Indeed, there I was repeating it from the note before THAT one that I’d been following up. I thought saying it a third time might be redundant. :-) But in case you missed it (lots of words, to explain a challenging issue), I’ll repeat it here:
“(Just remember what I said in my last note just now, about your needing to do a manual update to the IIS connector.)”
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Andrew Scott
Sent: Wednesday, August 12, 2015 3:37 AM
To: cfau...@googlegroups.com
Subject: Re: [cfaussie] CF and Windows 10 and IIS
Except that the installer will not finish the installation correctly, because the connectors will never get setup correctly. As they will not run on Windows 8 or above.
But if you know how to manually set them up, all will be good.
On Wed, Aug 12, 2015 at 5:09 PM, Charlie Arehart <charli...@carehart.org> wrote:
OK, here finally is what you can do, Mike (or anyone interested) to get things running.
I mentioned below that the “fusionator” blog post had talked about the process, and the key is that he suggests you extract the ColdFusion installer exe (yep, it is basically a zip, as an exe), and then he mentions “replacing the JRE” that comes with that with a more updated one (which does support Windows 8 or 10, such as Java 8 or perhaps later editions of Java 7). He doesn’t say anything more than that (about that process), so I assume he really meant “copy/paste” the JRE folder from an updated JVM to that folder in the extraction of the exe. (He also doesn’t give details about “what” JVM should be used. I will, below.)
While you can do that, you don’t really have to.
That same extracted folder (mine was C:\Users\charlie\Downloads\ColdFusion_9_WWEJ_win64\) will also have a \Windows folder, and in there will be a adobe_cf.lax, which is somewhat like CF’s jvm.config, as it’s a property file of
<snip>
Charlie Arehart
Hey Mike, any thoughts on this? (I saw your question on icann today, so I realize you may have more urgent priorities, but I just want to make sure you did see this and know you can get it working, pretty easily.)
/charlie
Mike K
Well, yes, I had set that yesterday. :-)
I didn’t think I needed to repeat it here, as it was the last sentence of the note which I responded to, with this later note being its follow up. Indeed, there I was repeating it from the note before THAT one that I’d been following up. I thought saying it a third time might be redundant. :-) But in case you missed it (lots of words, to explain a challenging issue), I’ll repeat it here:
“(Just remember what I said in my last note just now, about your needing to do a manual update to the IIS connector.)”
/charlie
Charlie Arehart
Thanks very much for the kind regards, and understood on the other priorities.
I really think you’ll find this will work, so hopefully you will be reporting good news when you get to try things. :-)
/charlie
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf Of Mike K
Sent: Friday, August 14, 2015 9:57 AM
To: cfaussie
Subject: Re: [cfaussie] CF and Windows 10 and IIS
G'day Charlie, And the others following this thread..