So I thought I’d spend my New Year’s Day messing around with some new CF10 features (namely sockets) on my development server with a 30-day-trial/developer edition to see if it’s something worth upgrading to this year, even though I’ve yet to find a single use relevant to any of my clients or any of the applications I’m creating (maybe I’ll find one right?).
I’m no IT admin, but I’m very adept with my way around Windows 2008 [R2] having used a Windows/IIS environment since Windows 2000 Server. I’ve also never had a problem with a CF install… to the point where I was comfortable enough with CF that with CF9 I wasn’t afraid to tinker with settings. Honestly, I don’t do anything special… I use a standalone instance of CF.
So when the “Cannot configure IIS connector” error popped up, it was no big deal to Google the error, open up the server roles and add the additional .NET services I was missing (I already had CGI installed for use with PHP… was just missing the others)… understandable.
I finished the installation with no problems. I clicked the done button to launch the configuration wizard and got a 500 internal server error.
I did a bit of my own troubleshooting and quickly discovered the ColdFusion service didn’t start. I also couldn’t manually start it. No biggy… server reboot… the service started… same 500 error.
Time for some more Google. Let’s see… I tried enabling 32-bit applications in my defaultAppPool… didn’t fix it. I tried the boncode connector… didn’t fix it, although that yielded an error that Tomcat wasn’t starting and I ran around Google for over an hour thinking that Tomcat was a separate service that wasn’t installed and why CF10 was broken, which wasn’t the case. I also tried a myriad of small setting changes in configuration files all over the place (bear in mind I’m reinstalling for each change… each uninstall was another 20 minutes which only worked when I manually stopped all the CF services AND IIS). And in a last ditch effort I thought I’d try to download and manually patch CF10 thinking an updated CF10 might just fix itself (I can’t even begin to describe how much of a pain in the butt it was to just find the links to download the patches… Adobe insists updating from the admin… what if you can’t login to the admin… or can’t get an outside connection because you’re on a military base… the feature is useless… so stupid Adobe… the files are here btw (mandatory | patch 1 | patch 2 | apparently patch 3 was bad | patch 4 | patch 5 | patch 6)). Well after a 45-minute wait staring at a progress bar that said “stopping the server cfusion” and seeing that the CF Windows services were definitely stopped, I gave up.
Judging by what I’m turning up from Google results, I’m not the only one running into these issues… in fact there’s too many installation problems to count, many of which reverted back to CF9. I’ve said it once and I’ll say it again, Adobe, this is exactly why you do thorough beta testing before you release the product. I was extremely frustrated I wasn’t included in beta testing… but was anybody included in beta testing of this product?
I spent 6 hours trying to INSTALL CF10… yeah I was done. Sadly (although it was very comforting), I reinstalled CF9 with ALL my custom optimizations in less than 30 minutes. Since my live server software directly mirrors that of my development server, it looks like I’ll wait for CF11 since there’s going to be a “more rapid release schedule” (won’t hold my breath on that one). And why would I recommend to anyone they pay for this? Are you listening Adobe? You guys assured everyone after the Macromedia merge you wouldn’t turn into them…. HELLO! I couldn’t even install the product to play with it!