Uderc programming article aggregator sites

How to Install Coldfusion 8 64-bit on Small Business Server 2008 64-bit

Answers: Have 3 answers
How to Install Coldfusion 8 64-bit on Small Business Server 2008 64-bit
I ran Coldfusion 8 on SBS 2003 Premium for 6 months with no problems.  When we finally decided to cut over to SBS 2008, that’s when everything went to hell.  I tried for weeks to get Coldfusion 8 to install properly on the new SBS 2008 64-bit box.  During the course which, I found bits and pieces of information for Vista 64-bit and Windows Server 2008 64-bit installations.  There are some distinct differences, however, with SBS 2008 since it runs core Web applications like OWA, RWW and Companyweb.  After countless unsuccessful attempts, one of which completed corrupted the box, I found the solution.
I have attempted in this white paper to detail the steps to assist others who may be in a similar situation.  I don’t make any warranty for the information, but so long as you follow the steps carefully you should be fine.  BTW, for those of you who say Adobe offers free technical support for licensed users, that’s not entirely true.  Like I said, I purchased CF8 and originally installed it on an SBS 2003 Premium box.  After we cut over to SBS 2008 and encountered problems, Adobe wouldn’t provide any technical support without charging.  Moreover, based on my initial conversations with Adobe’s technical team, no one seemed to know much about running 64-bit on SBS.
From my understanding, only two versions of Coldfusion 8 can be installed in 64-bit: Enterprise and Developer.  The “normal” install (which I paid a grand for) can only be deployed in 32-bit mode – gee, THANKS Adobe!  By the way, in Developer mode only two distinct IPs can access the site in addition to the localhost.  Any additional IPs will result in a CFML error message stating that the maximum number of IPs have been exceeded.  At any rate, take your time and follow the steps to achieve a successful installation. 
Back Up SBS
It’s always a good practice to backup your server before deploying any kind of major system changes.  Although this step is optional, I recommend it in case you need to restore your server for any reason.  Bear in mind, if your system ever gets totally corrupted, you cannot restore back from the twice daily incremental backup images alone.  You will need a full backup with system recovery information to restore.  Here are the basic steps:
Click: Start > Programs > Administrative Tools.  Right-click “Windows Server Backup” and choose “Run as administrator”.
Click “Backup Once” under Actions in the right-hand pane.
Choose the “Different Options” radio button under Backup Options.
Choose the “Custom” radio button.  What we’re primarily interested in here is backing up the OS – not your data partitions or attached drives.
Select the “SYSTEM (C)” checkbox, uncheck any others.  Also, ensure that the “Enable system recovery” checkbox is selected before continuing on.
Under ‘Specify Destination Type’, I usually select the “Local drives” radio button and point it to a Terrabyte USB drive I use for backups.  You can point this to a tape drive, or select the “Remote shared folder” radio button if you map to a UNC path to store your backup images.  Just remember, make sure that whatever path you select can readily be accessed in the event of an emergency.  Also, make sure the “Verify after writing (recommended)” checkbox is selected.
Under ‘Specified Advanced Option’, I usually select the “VSS full backup” radio button instead of the default since I don’t use a 3rd party backup product.  If like me you rely solely on SBS for your backups, choose the full backup option.
Confirm everything and click “Backup”.  This process may take several hours depending on the size of your system.
Verify ISAPI Filters:
In IIS Manager, double-click the server instance in the left-hand pane.
In the center pane under IIS, double click the “Modules” icon to verify that the ISAPI native modules are already installed for IIS.  If it’s set up correctly you should see two entries:
IsapiFilterModule              %windir%\System32\inetsrv\filter.dll
IsapiModule                        %windir%\System32\inetsrv\isapi.dll
If either of these modules are missing, you will need to re-install these (google for a solution).
Set Up Development Environment
Create a directory for your CFML files outside of the default Windows location (e.g., default is usually C:\inetpub\wwwroot\).  For the purpose of our install, I created a directory on a separate disk called: D:\DEV.
Copy and paste your CFML files and directories into the new DEV root Web directory.  This will eventually be the directory where the Coldfusion installer places the CFIDE and CFDOCS folders. 
Open IIS Manager and double-click the server instance in the left hand pane.  Expand the “Sites” folder.  Right-click the Sites folder and select “Add Web Site”.
Enter a name in the “Site Name” box (e.g., “test-site”).  You will notice that the system will automatically create a corresponding Application Pool with the same name.  NOTE: this is important to prevent conflicts between the DefaultAppPool (needed for SBS Web apps like OWA, RWW, etc.) and the application pool needed for Coldfusion to function properly in SBS 2008.
Point the “Physical Path” to the directory you created in step #1 above (e.g., “D:\DEV”).
Don’t worry about testing the connection.  If you click “Test Settings” you may receive a warning that IIS cannot verify access to path (D:\DEV).  Don’t worry about this for the time being.
Under “Host name”, enter a DNS path to your site (e.g., “dev.test-site.com”).  Click “OK”.
Configure Application Pools for Installation
In IIS Manager, double-click the server instance in the left-hand pane.  Click on “Application Pools” to display the list of server application pools in the center pane.
In the “Actions” pane on the right-hand side, click “Set Application Pool Defaults”.
Change “Enable 32-Bit Applications” - the second item from the top – from “False” to “True”, and then click “OK”.  NOTE: if you skip this step, Coldfusion will not properly create the required mappings during the install. We will change this setting back after the installation completes – more on this later.
Modify the application.host.config File for 64-Bitness
Click: Start > Programs > Accessories.  Right-click “Notepad” and choose “Run as administrator”.
Open the config file from within Notepad – default location: C:\Windows\System32\inetsrv\config\applicationHost.config
Do a search and change this one line from:
<add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" />
To this:
<add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" preCondition="bitness64" />
Restart the IIS Admin service.
Set HTTP Compression
According to some threads I read, the http compression module can cause errors if you don’t disable it globally. To remedy this, perform the following:
Click: Start > Programs > Accessories.  Right-click “Command Prompt” and choose “Run as administrator”.
At the command prompt, change directory to intetsrv by typing: cd inetsrv
Run the following command:
C:\Windows\system32\inetsrv>appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
This will turn off HTTP compression for all sites in IIS.
In IIS Manager, double-click the server instance in the left-hand pane.  Double-click the “Compression” icon in the IIS section of the center pane.
Uncheck all of the boxes, then click the “Apply” button under Actions in the right-hand pane.
Recheck all of the boxes, then click the “Apply” button under Actions in the right-hand pane.
Restart the IIS Admin service.  This should enable compression and coldfusion to work at the same time.
NOTE: if for some reason you need to reverse this, run the following command from the command prompt:
C:\Windows\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+[name='xpress',doStaticCompression='false',dll='%windir%\system32\inetsrv\suscomp.dll']
Download the 64-bit installation package from Adobe – filename: coldfusion-801-wind64.exe.
Right-click the file and select “Run as administrator”.
Accept the terms of the License Agreement.
If you have an Enterprise license, enter it.  For our purposes, just click the “Developer Edition” checkbox.
Select “Server configuration” – the default radio button.
I deselected all subcomponents and can’t guarantee that you’ll arrive at the same results if you select additional items like “.NET Integrated Services”.  It should be fine, particularly if you install documentation.  My preference was to keep the install as plain vanilla as possible.
Select the directory path for Coldfusion to install into – default is :C\Coldfusion
THE NEXT TWO STEPS ARE CRITICAL TO YOUR SUCCESS.  Unselect “All IIS Websites” and select the “Configure specific IIS Website or another web server” radio button.  Click “Add”, and then select your test Web site (e.g., “test-site”) under “IIS Web Site”.  Hit “OK”.
Do NOT use the default directory path for the CF Administrator location (e.g., default path: “C:\inetpub\wwwroot”).  Instead, point the installer to your new DEV root Web directory (e.g., “D:\DEV”).  The bottom line, you want the installer to place the CFIDE directory and files within this folder, alongside your other CFML files and folders.
Enter an Administrator password.
Choose to Enable RDS, or not.  I enable this by preference but it is not required.  This allows you to make updates to files using a CFML editor directly vs. having to move/FTP the files over if you’re working remotely.  Opponents to this argue that it’s potentially less secure, but for a lower environment I don’t see this as a major concern.
Confirm everything to kick off the install.
If all goes well you should see a message at the end stating that the install was successful.  I recommend you uncheck the box that asks you to open the CF Administrator in the default Web browser after the install.  NOTE: we will open it a different way during the post-installation tasks.  The worst thing that will happen if you forget to uncheck the box is that you might receive an error that the command prompt hung – not a big deal – just close it and move on to the next (final) steps.
Verify CF Installation:
The installation will create a new folder in your program group: Start > Programs > Adobe > Coldfusion 8.  The default “Administrator” link will not work because it points to the wrong path: The “” or “localhost” path as you may recall in IIS, points by default to the “C:\inetpub\wwwroot” directory.  Our CFIDE files, however, are located within: D:\DEV.
To bring up the CF Administrator logon page, open up a Web browser and replace the “” part of the path with the DNS path name to your CF environment (e.g., http://dev.test-site.com/CFIDE/administrator/index.cfm).
This should bring up the Coldfusion Administrator Login screen.  Enter in the Administrator password you created during the install to log in and configure your application server.
Verify that your test-site renders correctly by typing in your test URL into a Web browser (e.g., http://dev.test-site.com).
Fix Application Pool Defaults to Re-enable SBS Web Applications:
At this point, Coldfusion Administrator and your test CMFL Web site should be working properly.  The problem is, default SBS Web applications like OWA, RWW and Companyweb will throw errors and fail to start.  Fortunately, this is easily remedied by performing the following steps:
In IIS Manager, double-click the server instance in the left-hand pane.  Click on “Application Pools” to display the list of server application pools in the center pane.
In the “Actions” pane on the right-hand side, click “Set Application Pool Defaults”.
Change “Enable 32-Bit Applications” - the second item from the top – from “True” to “False” this time.  This should re-enable the SBS applications, which would otherwise result in 500 errors (e.g., OWA, RWW, Companyweb, etc.).  There is no need to restart IIS.
Open a Web browser and test that you can once again connect to OWA, RWW and Companyweb successfully.
In IIS click to highlight the application pool for your new site (e.g., “test-site”).  In the right-hand pane, click “Advanced Settings”.  Ensure that “Enable 32-Bit Applications” – second item from the top – is set to “True” for this application pool specifically.
Lastly, jump up and down for joy!  Hopefully now, everything is working.  Best of luck!! ..Paul D (MCP).
The best answer: First, it would be a good idea for you to specify what distro of Linux you're using, as not all are supported by Adobe.
Second, this is probably your problem right here:
In a nutshell, CF expects the 32-bit version of libc.so.6 to be in /lib, but it's probably not. You might be able to modify the installer to point to the correct location for that file, or you might be able to create a symlink to the file - but as the above link describes, creating a symlink might have negative consequences.
As for installing CF 8 64-bit, that's only available with Enterprise, not Standard. If you want CF Standard 64-bit, you need to upgrade to CF 9.
Dave Watts, CTO, Fig Leaf Software