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: cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] On Behalf Of Charlie Arehart Sent: Wednesday, 12 August 2015 5:10 PM To: cfaussie@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 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 From: cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] On Behalf Of Charlie Arehart Sent: Tuesday, August 11, 2015 6:38 PM To: cfaussie@googlegroups.com Subject: RE: [cfaussie] CF and Windows 10 and IIS 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 From: cfaussie@googlegroups.com <mailto:cfaussie@googlegroups.com> [mailto:cfaussie@googlegroups.com] On Behalf Of Charlie Arehart Sent: Tuesday, August 11, 2015 9:41 AM To: cfaussie@googlegroups.com <mailto:cfaussie@googlegroups.com> Subject: RE: [cfaussie] CF and Windows 10 and IIS 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: cfaussie@googlegroups.com <mailto:cfaussie@googlegroups.com> [mailto:cfaussie@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. I had a WIndows7 machine. With ColdFusion 9 Enterprise. That's my dev environment at the moment. I upgraded windows to WIn10 Home and Apache didnt work. That's where this whole thread started. And I havent found a way out of it yet, apart from moving CF up to CF11. As it turns out, ColdFusion 9 might run on any version of windows, but however its bloody well not running on my WIndows10 Home machine. It wont even run the installer. I have 4 machines to deal with. The machine I'm working on at present is the one i rarely use, but having any of the others out of action for more than a day would be a big problem. So i need to figure out what my strategy is going to be before I even start on those ones. -- 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 <mailto:cfaussie+unsubscr...@googlegroups.com> . To post to this group, send email to cfaussie@googlegroups.com <mailto:cfaussie@googlegroups.com> . Visit this group at http://groups.google.com/group/cfaussie. For more options, visit https://groups.google.com/d/optout. -- 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 <mailto:cfaussie+unsubscr...@googlegroups.com> . To post to this group, send email to cfaussie@googlegroups.com <mailto:cfaussie@googlegroups.com> . Visit this group at http://groups.google.com/group/cfaussie. For more options, visit https://groups.google.com/d/optout. -- 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 <mailto:cfaussie+unsubscr...@googlegroups.com> . To post to this group, send email to cfaussie@googlegroups.com <mailto:cfaussie@googlegroups.com> . Visit this group at http://groups.google.com/group/cfaussie. For more options, visit https://groups.google.com/d/optout. -- 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.
