FYI, we found the issue with this: After a third developer did an install with the exact same result, running diff on configuration files against a clean install showed the problem.
Each developer had previously been running CF8. Created a .car file of their settings. Uninstalled CF8, rebooted. Installed CF9 64-bit developer, rebooted. Restored .car file. System ran fine until services got restarted at some point -- either through a reboot or simply restarting the services for some other purpose. jvm.config as well as numerous other settings files showed essential paths pointing to \Coldfusion8 rather than \Coldfusion9. Fixing these paths resolved the problem. The same installation process was followed for 32-bit installations on XP machines. These workstations had no problem, and showed no path problems in jvm.config or other files. Cheers, Kris On Thu, Apr 15, 2010 at 11:28 AM, Kris Jones wrote: > We'll be running on Windows Server 2008 in production (and dev & stage > environments). > > But we do need to get this issue resolved for our developers local > machines as well. > > On Thu, Apr 15, 2010 at 11:22 AM, Dave Watts wrote: >> >>> Incidentally, CF9 32-bit has been running flawlessly, but we want to >>> be running 64-bit in production so need to have this resolved. >> >> But you're not going to be using Windows 7 in production, right? Could >> you try running it in a VM with your production OS (Windows Server >> 2008?) I realize that's kind of a pain, but we've been running CF 9 >> 64-bit on Windows Server 2008 with no problems. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:332967 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
