Installing ColdFusion 9 64-but on Windows 7 64-bit Experience

This weekend I got me a new laptop from Dell (Studio 15). I got it with 4 GB RAM (to me it has become a minumum now) which naturally meant going with a 64-bit OS. So, I now had this nice new laptop with Windows 7 x64 and once I was done cleaning out the bloatware, it was time to install ColdFusion. It turned out to be quite an experience and took much longer then I anticipated. But first, lets get one thing straight here, Adobe doesn't really provide any documentation on what you need to do to install CF properly on IIS 7.5. There is no, "verify these windows component are installed" document or screen. In any case, I had installed ColdFusion 9 on Windows 32-bit succesfully, and needless to say I felt (over)confident that I could do the same for Windows 7 64-bit.

I started out by configuring Windows have the IIS6 modules installed, I knew I had to do that. Then I ran the ColdFusion 9 install, no errors, got to the end, "Press OK to start CF Admin", did that. The CF Admin screen came up and did not work. IIS 7 told me about missing extension configuration. I realized at that point something was missed in my IIS reconfiguration, and it turned out it was the ISAPI Extensions under World Wide Web Services options, so I turned all those things on, Windows reconfigured IIS for me. I opened IIS, saw tha the ISAPI extensions and filters were not installed. Ready to go right? Wrong.

Still could not get to CF Admin. Ok, lets uninstall and install CF9 I thought, since now IIS has everything it needs for proper configuration. So I did that, uninstall then install and once again pressed "OK" at the end. Out comes the CF Admin page, "Click here" to continue configuration. Yay, victory was my first though. But then I noticed, something was not right. There was no Adobe logo, no images were showing up. Doesn't matter, I was able to open a .cfm page, so I continued with the configuration and then was logged into the Admin. Still no images. By the way, the Admin looks really bad if you can't see images. So, I closed the browser and opened a new IE window and went to //localhost/cfide/administraor/ and IIS 7 gives me an Error!! But thats where the CF Admin is located, but apparently IIS can't handle the request properly.

Sigh, I did some googling. Verified that the ISAPI handlers for .cfm extensions were pointing to the right DLL. Someone suggested uninstalling CF, deleting all CF directories and installing again. So I dd that, but same error again. Still can't see images in CF Admin. Frustrating, already installed CF9 3 times. Verified IIS setup again, all looks good there. I uninstall CF9 again, restart computer, delete directories, install CF9 again and same issue again. At that point, google had helped me as much as it can. I try to use the server configuration tool but I can't remove the current flawed IIS configuration from it (some error about not able to remove things).

Decide it time to start from scratch. So, I uninstall CF9, delete CF directories, restart computer. Uninstall IIS7 from windows, restart computer. Then reinstall IIS7 and restart computer. Then reinstall CF9 and Victory!! Everything works properly. Apparently, installing the ISAP Extensions after installing CF9 screwed up the installs and configurations in IIS. So, well, it worked now. Logged into CF Admin, //localhost/cfide/administrator/ resolved properly.

But that was not the End of the Story.

Apparently, setting up a MS Access Datasource on Windows 64-bit is another issue faced by various users. You would get an error about DRIVERPATH not defined. Well I thought, if CF can't set it up, I will set it up in Windows and use ODBC socket. But the issue is that the 64-bit Windows don't come with the relevant drivers needed to setup Access Datasource in Windows. After trying to figure out how to resolve this, googling and finding some information here and there, not much help was found. In the end it was realized, that the Windows\System32\odbcad32.exe file contained the proper drivers but the Windows\SysWOW64\odbcad32.exe did not contain the drivers. So the solution was to copy over the .exe from System32 to SysWOW64. I went through with that and it worked!! Even though, ColdFusion still gave a DRIVERPATH undefned error, the datasource was verified properly and I could run all my MS Access based demos.

Whew, finally, was done with setting up Coldfusion 9 64-bit on Windows 7 64-bit.

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)
Jonathon Joyce's Gravatar I guess i was lucky then! It took me less then an hour to set mine up....
Default IIS installation from dell (Optiplex 780 desktop) and then the EAR/WAR CF9 installation...
# Posted By Jonathon Joyce | 2/16/10 1:21 PM
Mark Fuqua's Gravatar Thanks for the post...I'm having the same problem with MS Access and Vista on 64 bit...I looked for the file you mention and the only one I can find was Windows\System32\odbcad32.dll not a .exe.

Do you think that might be the same file/issue? Also, sorry to display my ignorance, but if I do copy the file over to Windows\SysWOW64\odbcad32.dll and it is not needed or used, will it cause any errors?

Thanks,

Mark
# Posted By Mark Fuqua | 2/16/10 2:18 PM
Andy K's Gravatar Office 2010 is slated to come out any day now (I believe you can download the RC to play with it?) This version also comes with a 64-bit version of each application (including Access)

Does anyone know if this will make it easier to setup MS Access on 64-bit CF?
# Posted By Andy K | 2/16/10 2:54 PM
Kumar Shah's Gravatar @Mark, I am not sure. If you try anything like that, make sure to take proper backups. I think you should have the .exe too, if you don't try and check what .exe is opened when you open Administrative Tools->ODBC (the .exe opens the same window).

@Andy, I am not sure of that either. Its worth a try, though. I know that currently MS has a "Office Datasources" tool you can download that is supposed to add the Drivers to Windows allowing use of them, but for 64-bit Windows it installs them for System32\ and not SysWOW64\
# Posted By Kumar Shah | 2/16/10 3:16 PM
Tony D.'s Gravatar Tried out Coldfusion Builder and it told me I should restart the Coldfusion Server after changing some settings, so I shut down Coldfusion8 from within Coldfusion Builder and that was that, it never started again.
No prob, time to upgrade to CF9.
First thing I noticed was that CF9 uses localhost (no :8500) and mentions port 80 but doesn't accept http://localhost:80.
Anyway just using http://localhost works fine for Coldfusion functionality but neither the CSS nor images render.
Using DW10 it works fine in Liveview but not in any browser. It doesn't show images or flash movies (silly message about updating Flash Player appears).
Tried reinstalling etc and took a long walk at lunch to avoid kicking the computer out the window. Computer is still intact, CF Builder is history and I'm thinking of going into therapy. ' It all started with some simple upgrades...
# Posted By Tony D. | 5/5/10 1:50 PM
Tony D.'s Gravatar As the issue is essentially a relative address problem almost embarrassed to say I tried the following:

cfif FindNoCase('localhost',cgi.server)
base href="http://localhost/mySiteFolder";
cfelse
    base href="http://www.myServer.com";
/cfif
This sorted the images but not the CSS. Selecting the 'Preview using temporary file' in DW CS4 preferences sorts the CSS but why?
The Flash movie still doesn't display citing a security issue. Silly stuff.
# Posted By Tony D. | 5/5/10 2:42 PM
Guillermo Dewey's Gravatar having the same problem but I am installing on windows 2008 server 64 bits (exact same diag as you on win 7)

Following your advice I am uninstalling everthing and restarting. then installing and restart all.. lets see how it does

canot belive why adobe releases cf with out testing a regular 64b server installation. reminds me the first versions of cf when allaire was aquire by macromedia..

only reason I came back to cf is because of the existance of cf builder..
# Posted By Guillermo Dewey | 5/21/10 9:52 PM
HMC's Gravatar Thank you for your very useful post. It was very helpful and enabled me (finally) to install CF9 64bit on a Windows 7 Pro 64bit laptop. For anyone reading this post, two other tips: Restart your computer after installing and configuring IIS (as this post indicates) and then check that IIS is running correctly (browse to http://localhost ... and check that the IIS Welcome Page appears) BEFORE trying to install CF.
Thank you again!
# Posted By HMC | 5/26/10 4:47 PM
Greg Miller's Gravatar Thanks for your post. I went through much of the same grind before finding your page. I thought I was being smart by upgrading my Office installation to 2010 64 bit (Win 7 64 & CF 9 64). When I try to define the data source using the ODBC socket or as a Microsoft Access Database, I get an error:
"The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application"
If anyone has any ideas, I would appreciate it. If I find the answer, I'll be sure to come back and post it.
Thanks for your time.
# Posted By Greg Miller | 6/11/10 10:57 PM
StellaBob's Gravatar New computer...Windows 7, CF9, MS Office 2010...same issue. I found this thread and got very excited, but when I searched for odbcad32.exe, it shows that file in both the Windows/System32 folder and the SysWOW64. Any other suggestions?
# Posted By StellaBob | 7/1/10 10:50 AM
BlogCFC was created by Raymond Camden. This blog is running version 5.9.5.003.  Design based on ARCLITE by: digitalnature