Friday
Nov302007
Installing Coldfusion 8
Friday, November 30, 2007 at 16:57
Having a day off from work meant that I had some time to clean-up my server from everything crap. This also meant trying to upgrade Coldfusion MX 7 to Coldfusion 8. The new version supports some nice new features, with which I wanted to experiment.
Since none of my production websites run on Coldfusion (currently PHP), I could safely uninstall and install the new developer version. When I pressed 'remove' I had this flash from the past. When I tried to install version 7 I had humongous problems with the installer (services didn't register correctly with IIS, etc.). But this could be just a coincidence...
Installing Coldfusion itself was straight-forward. The fun began when the installer wanted to launch the admin-panel to finalize the installation. No responds from the webserver. Even my blog was not working ("System cannot find the file specified"). Seemed that there were references to the old Coldfusion parser in the IIS.. After removing those instances, I had my blog back up-and-running.
Next was to finalize the Coldfusion 8 installation. I had to manually add the Coldfusion parameters to IIS (allowed Web Services, document types, ... the works) After screwing around for nearly two hours, I could finish the installation.
Just to make sure that it wasn't me, I installed it also in a virtual machine. And off course it worked flawlessly. Guess I need to reinstall my server in the next couple of weeks. Who knows what else is f*cking up the system.
Oh, another thing; I used to use RDS for development of the websites, so I tried to configure it again.... Well you might guess it... Not working. After yet another hour searching I found that RDS uses a 'virtual file' called 'ide.cfm'. This file is located in /CFIDE/main/. The actual location (main/) doesn't exist, so IIS returns a 404 error.
It seems that you need to uncheck 'Verify if file exists' in IIS for the .cfm extension for RDS to work. Or do as I did; create the directory 'main' and create an empty file called ide.cfm in that directory.
Well, this was an afternoon well spent.... NOT.
Next mission is to upgrade MySQL to version 5. So expect some serious downtime.
UPDATE: MySQL has also been upgraded to v5.something. It went surprisingly easy.
Since none of my production websites run on Coldfusion (currently PHP), I could safely uninstall and install the new developer version. When I pressed 'remove' I had this flash from the past. When I tried to install version 7 I had humongous problems with the installer (services didn't register correctly with IIS, etc.). But this could be just a coincidence...
Installing Coldfusion itself was straight-forward. The fun began when the installer wanted to launch the admin-panel to finalize the installation. No responds from the webserver. Even my blog was not working ("System cannot find the file specified"). Seemed that there were references to the old Coldfusion parser in the IIS.. After removing those instances, I had my blog back up-and-running.
Next was to finalize the Coldfusion 8 installation. I had to manually add the Coldfusion parameters to IIS (allowed Web Services, document types, ... the works) After screwing around for nearly two hours, I could finish the installation.
Just to make sure that it wasn't me, I installed it also in a virtual machine. And off course it worked flawlessly. Guess I need to reinstall my server in the next couple of weeks. Who knows what else is f*cking up the system.
Oh, another thing; I used to use RDS for development of the websites, so I tried to configure it again.... Well you might guess it... Not working. After yet another hour searching I found that RDS uses a 'virtual file' called 'ide.cfm'. This file is located in /CFIDE/main/. The actual location (main/) doesn't exist, so IIS returns a 404 error.
It seems that you need to uncheck 'Verify if file exists' in IIS for the .cfm extension for RDS to work. Or do as I did; create the directory 'main' and create an empty file called ide.cfm in that directory.
Well, this was an afternoon well spent.... NOT.
Next mission is to upgrade MySQL to version 5. So expect some serious downtime.
UPDATE: MySQL has also been upgraded to v5.something. It went surprisingly easy.
Reader Comments