Entries Tagged as 'Connector'

You might want to set up ColdFusion in a distributed environment where ColdFusion is running on one machine and Web server is running on a different machine.

Following are the set of steps that have to be performed to achieve this (less error-prone):

This applies to both ColdFusion 10 and ColdFusion 11.

1) Have ColdFusion server installed in a machine.

2) Next thing is to download and install VC Runtime.

             - The version of VC Runtime that you have to install depends on the version of ColdFusion.

                Say, ColdFusion 11 needs VC Runtime 2012

                 (32-bit VC Runtime for 32-bit Web server and 64-bit VC Runtime for 64-bit Web server.

                  If you are not sure, you can install both)


                and ColdFusion 10 needs VC Runtime 2010


3) Copy the following contents from the machine where ColdFusion is running to the machine where Web server is running at the same location.





4) Open a Command prompt and run wsconfig tool

   C:\ColdFusion11>jre\bin\java -jar cfusion\runtime\lib\wsconfig.jar

    It will open a configuration window where you have to provide AppServer Host as the ColdFusion Server IP.

    Configure the connector.

Distributed environment is ready for use. Send requests to the Web server's URL with cfm files under web server root and same files under ColdFusion's Web root.

Web server would redirect these to ColdFusion, which is on some other machine.



I have seen many customers getting confused in custom error pages and onMissingTemplate feature in ColdFusion and IIS. So I thought of blogging it for the use of larger audience. Before starting let me setup a platform.

Customer Eddard(name assumed) is using ColdFusion10(valid for ColdFusion11 too) configured with IIS. He has setup onMissingTemplate in Administrator of ColdFusion. Now Eddard expects ColdFusion to run this error page(mentioned in onMissinTemplate), let's call it 404.cfm, whenever user hits a page which doesn't exist. But suprisingly his browser is not showing the contents of 404.cfm and instead showing IIS 404 error page which is a static file(html file). After a lot of struggle he finds another confusing behavior that when he access the non existing page from machine where server is running(localhost) then his 404.cfm is getting executed. It's clear from the behavior that there is somehting in IIS which is handling this behavior.




You guys must be thinking what is the right approach then. I will give three scenarios and you can chose any one depending upon your requirements.
1. Custom error page - Simply use custom error page and do not use onMissingTemplate. You have to opt for "Custom error pages" in "IIS->site->error pages->edit feature settings". And give a 404.cfm url against required status code like 404 in "IIS->site->error pages". This cfm will be executed whenever that error has been hit like a user requested for non existing page. The page will not be executed twice since you have not mentioned anything in onMissingtemplate.





We have seen that some of you have not been able to get the web server connector working after applying update 14.

We did our investigation and following is our finding.

The connector binaries of ColdFusion 10 update 14 are built on top of  VC++ runtime 2012 update 4.

Installation of VC++ runtime requires admin privileges. If the ColdFusion service runs as administrator or system account, the update itself install the VC++ runtime as this account would have installation privileges.

If your ColdFusion service account is not running as administrator or system account, applying the hotfix from administrator can't install VC++ runtime and you will get "500 internal server error" after configuring the connector.

In this case, you need to manually install VC++ runtime 2012 32-bit and/or 64 bit depending on whether Web server is 32-bit or 64-bit.

You can download VC++ runtime here at:


When you install hotfix manually, administrator privileges are enforced and so the installation of VC++ runtime is automatically taken care by the updater.





Connector tuning is an essential part of setting up a ColdFusion server. There are various configurations in connector that needs to be tuned. Incorrect values may lead to “Service Unavailable” or “Server too busy”. In this blog, we will discuss how to handle such errors caused by incorrect tuning and how to tune the connectors for the site correctly.


ColdFusion 10 Update 11(http://helpx.adobe.com/coldfusion/kb/coldfusion-10-update-11.html has been released which includes support for 64-bit COM interoperability, Microsoft SQL Server 2012 and MySQL 5.6 in addition to several important bug fixes.This update includes a fix for bug 3488063 - IIS 404 custom error handler URLs that are .CFM files do not consistently return entire document .

Though the wsconfig.jar(present in ColdFusion10\cfusion\runtime\lib,which is required for configuring connectors) has been  modified for the above mentioned bug ,it is not required to re-install the connector in all the cases.

If you are on ColdFusion 10 Update 5 or later and are using IIS webserver,you must either re-install/reconfigure the connector or use the command line interface and run the '-upgrade' option.The '-upgrade' option upgrades existing configured connectors with newer modules from a newer wsconfig.jar file.

<cf_root>/runtime/bin/wsconfig.exe -ws iis -upgrade -site <site name/ID>

If you are on ColdFusion 10 Update 5 or later and are using Apache webserver , you don't need to re-install/reconfigure the connector as the fix was specific to IIS webserver and the Apache connector files remain the same.

If you are not on ColdFusion 10 Update 5 or later then you will have to re-install/reconfigure the connector for update 11.If you are on ColdFusion 10 Update 5 or later and have not re-installed/reconfigured the connector earlier  then you will have to re-install/reconfigure the connector for update 11.


- Asha