Home / Products / ColdFusion / Support / Release Notes
Macromedia ColdFusion Support Center Release Notes

ColdFusion MX 6.1 Known Issues

Updated April 21, 2005

This document lists the issues and limitations with ColdFusion MX 6.1 that were known at the time of this release. For information on confirmed issues that are discovered after the release date, see TechNote 18795

For Release Notes and issues resolved in the release, see the following web pages:



ColdFusion MX J2EE configuration: The variable attribute of the cfregistry tag is not available after a registry key, string, or /value is read from the registry. As a result, the ColdFusion MX Administrator cannot add a data source for the Access driver or the ODBC Socket driver. To work around this issue, add the path to cfusion\\WEB-INF\\cfusion\\lib to the JNI path of the underlying J2EE server. This is not an issue with the ColdFusion MX server configuration.
If RDS is disabled, you cannot use the Browse buttons in the ColdFusion MX Administrator.

CFML functions

Note: Other sections of this document also list issues that affect specific functions.

When using query data that was created by the QueryNew function, in some cases data might be converted to the wrong type; for example, '14 946 039 485' might become '14946039'. This problem does not happen with query data retrieved from a database using the cfquery tag.

Back to Contents

CFML tags

Note: Other sections of this document also list issues that affect specific tags.

If you delete a scheduled task by using the cfschedule tag, the task continues to run as previously scheduled even though it has been deleted. To stop the deleted task, stop and restart the ColdFusion MX application server service. For more information, see TechNote 18361.
The value in the queryname.UID field returned by the cfpop tag does not contain the POP UID; it contains the value of the Message-ID header. As a result, if you use the queryname.UID field value to identify the message to delete in a cfpop tag, and the message lacks a Message-ID header, the message is not deleted. To work around this problem, use the queryname.MessageNumber value to get or delete a message if the queryname.UID field is empty.

ColdFusion components and user-defined functions

The Arguments scope array of CFCs has an empty first element if an argumentCollection structure is passed to a method.
A page included by using the cfinclude tag within a cffunction tag in a CFC cannot use a cfreturn tag. The cfreturn tag must be outside of the included page.

Back to Contents

Database and query of queries

When using SQL Server 2000 with the ColdFusion MX 6.1 Microsoft SQL Server driver, some variable names that are contained in result data from stored procedures differ from those used by the ColdFusion 5 Microsoft SQL driver or the ColdFusion MX and ColdFusion MX 6.1 ODBC Socket driver. For detailed information on the differences, see TechNote 18796.

A query of queries SELECT statement that includes the like operator generates errors if used with a null column. For example, if the lastName column contains null entries, the following code generates an error:

select * from myquery where lastName like '%F%'

To work around this issue, use code such as the following:

select * from myquery where lastName is not null and lastName like '%F%'


To connect to Informix databases that have certain character sets, you must add the following lines to the file macromedia/util/ that is contained in the cf_root\WEB-INF\cfusion\lib\macromedia_drivers.jar archive file. Extract the file, inset the lines, and import the updated file back into the JAR file to replace the original copy in the file. You can then delete the extracted copy.

translit.alias.57350=SJIS # Informix "sjis"
translit.alias.57351=EUC_JP # Informix "ujis"
translit.alias.57372=UTF8 # Informix "utf8"
translit.alias.57375=EUC_TW # Informix "euctw"

For installations using JRun, the neo-query.xml and jrun-resources.xml files are no longer synchronized. As a result, JRun users running the J2EE configuration must add data sources to both ColdFusion (neo-query.xml) and JRun (jrun-resources.xml).
WebSphere 5 data sources use Java Connector Architecture (JCA), a more generic means for integrating data providers to J2EE application servers. ColdFusion MX 6.1 supports JDBC data sources, but not JCA data sources.
You might receive a misleading "Timed out trying to establish connection" error rather than the database server's native error (such as "bad password") if the database doesn't respond in 30 seconds, which is the login timeout default.
You cannot use CLOB or BLOB data with the Oracle Thin Client driver on ColdFusion MX. Use the Oracle JDBC driver that ships with ColdFusion MX Enterprise instead.
The Access with Unicode driver uses the Microsoft JET Database Driver. Therefore, all SQL in queries using this driver must conform to the JET Driver's syntax, including its list of reserved words. For more details, see

Under some circumstances, if Microsoft SQL Server closes a connection unexpectedly while processing a long-running query, the DataDirect 3.2 JDBC database driver provided in ColdFusion MX 6.1 may respond inappropriately, continuing to wait for a DB server response while unnecessarily consuming CPU resources. When this occurs, a Java stack trace shows a thread stuck at a function called "empty()":

"jrpp-10" prio=5 tid=0x6403b958 nid=0x554 runnable
[6938e000..6938fdb8] at macromedia.jdbc.sqlserver.
SQLServerByteOrderedDataReader.empty (Unknown Source).

This issue does not exist in ColdFusion MX versions through Updater 3.

An updated version of the 3.2 driver for ColdFusion MX 6.1 that responds correctly to this condition is available at the Macromedia website.


The ODBC Agent service and ODBC Server service write an error message similar to the following to the application event log when you install ColdFusion MX 6.1. You can safely igore these errors.

The description for Event ID ( 0 ) in Source (ColdFusion MX ODBC Server) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: ColdFusion MX ODBC Server error: 0, StartServiceCtrlDispatcher Error!.

Back to Contents


The following documentation issues exist in the printed documentation, the downloadable files, and the HTML that is provided in the ColdFusion MX 6.1 installation. For the most up-to-date versions of the documentation, see the Macromedia LiveDocs system.

The HTML documentation that ships with ColdFusion MX 6.1 uses a Java applet to render the table of contents, for index lookup, and for searching. The JAR and CAB files that contain this applet use VeriSign certificates that expire, as follows: - Expires 8/15/03
wwhelp3.jar - Expires 5/30/03

As a result, after these dates, on some browser configurations you might get a dialog box warning that the certificates have expired when you first use the ColdFusion MX 6.1 HTML documentation. This does not represent a security concern. (Note: You should not deploy the cfdocs directory on production or public servers, independent of this issue.)

Macromedia plans to post a ZIP file that contains updated documentation with replacement JAR and CAB files. For more information on the updated ZIP file, see
In Getting Started Building ColdFusion MX Applications, the code in "Exercise: enabling the departure and price criteria on the Trip Search form" used to identify the date in the SQL query is incorrect for a Microsoft Access database.

In the code that adds the date information to the WhereClause variable in the SQL statement, you must put each reference to Form.departureValue inside a CreateODBCDate function, as follows:

<cfif Form.departureValue GT "">

  <cfif Form.departureOperator EQ "EQUALS">

    <cfset WhereClause = WhereClause & " and departureDate

= " &       CreateODBCDate(Form.departureValue)>

  <cfelseif Form.departureOperator EQ "AFTER">

    <cfset WhereClause = WhereClause & " and departureDate > " &       CreateODBCDate(Form.departureValue)>

  <cfelseif Form.departureOperator EQ "BEFORE">

    <cfset WhereClause = WhereClause & " and departureDate < " &       CreateODBCDate(Form.departureValue)>



This forces the string into a standard Date format that Access (and other databases) can understand.
The description of the cfhttp tag in the CFML Reference incorrectly states that the default port for HTTPS is 413. The default port for HTTPS is 443 .
If you install the ColdFusion MX 6.1 J2EE configuration, or install JRun 4 and the J2EE configuration, the Configuration Wizard does not include an option to disable RDS. If you deploy ColdFusion MX and want to disable RDS, you must do it manually, after you deploy ColdFusion MX. The printed installation documentation does not reflect this late change to the wizard. The online versions of the documentation do include this information.
The CFML Reference entry for the GetToken function incorrectly states that the comma is the default list delimiter. There is no default list delimiter for the GetToken function.

The CFML Reference entry for the cfchart tag does not document the backgroundColor attribute. The following information is missing from the table:

Attribute: backgroundColor
Required/Optional: optional
Default: white
Description: Color of the area between the data background and the chart border, around labels and around the legend. Can be a hexadecimal value or a supported named color; see the name list in the cfchart reference Usage section. For a hex value, use the form "##xxxxxx", where x = 0-9 or A-F; use two pound signs or none.

Installing and Using ColdFusion MX has the following typographical errors in the Configuration subsection of the "ColdFusion MX J2EE deployment and configuration" section of Chapter 3, "Installing the J2EE Configuration."

In the CORBA instructions, cf_root should be italicized and the quotation marks are not required. The corrected text is a s follows:

CORBA (optional) Copy vbjorb.jar to WEB-INF/cfusion/lib and define the following argument:

In the charting instructions, $cf_root should be italicized, and should not have a dollar sign. The following is the corrected text:

Charting Define the following argument (or ensure that WEB-INF/cfusion/lib is in the JVM's classpath):

In the Charting (UNIX Only) instructions, the trailing quotation mark should be omitted. The following is the corrected text:

Charting (UNIX only) Define the following argument:

The CFML Reference entry for the cfpop tag contains the following paragraph:

The queryname.attachments column contains a tab-separated list of all the attachment names. The queryname.attachments column contains a tab-separated list of the locations of the attachment files.

The second mention of queryname.attachments should be queryname.attachmentfiles
The CFML Reference entry for the cfexecute tag incorrectly states that ColdFusion reports an "'Application File Not Found" error if the application name is not found. The reported error is a exception.
In the CFML Reference entry for the cfdirectory tag, the description for the sort attribute incorrectly lists ac as an attribute value. The correct value for an ascending sort is asc.
The Usage section of the CFML Reference entry for the cfparam tag refers to specifying variableName for the returnType attribute. It should refer to specifying variableName for the type attribute.
In the CFML Reference entry for the ParseDateTime function, the description for the date/time string parameter incorrectly states "years 30-99 are interpreted as 1990-1999". The correct statement is "years 30-99 are interpreted as 1930-1999 ."
The table of contents tree in the Japanese ColdFusion MX Administrator online Help contains links to files that are no longer part of the online Help system.
Configuring and Administering ColdFusion MX has errors in its discussions of multihoming with IIS. For more information, see TechNote 18798.
The "Passing parameters in direct method invocations" section of Chapter 11: Building and Using ColdFusion Components of Developing ColdFusion MX Applications refers to an argumentsCollection structure. The correct name is argumentCollection.

Back to Contents

Exception and error handling

Missing template handler pages of less than 512 bytes might not display in Internet Explorer browsers due to a default Internet Explorer "errorthreshold" page size setting. When pages are smaller than 512 bytes and "Show Friendly HTTP error messages" is selected in Internet Explorer, Internet Explorer produces its own "Page Not Found" message and throws out the page sent from the application server. For more information, see the Description of HTTP Error Messages Knowledge Base article at the Microsoft website.

Back to Contents

General server

On extremely slow or very heavily loaded Windows systems, the main ColdFusion MX Application Server service might not automatically start on system restart using the default service startup timeout values. For more information, see TechNote 18799.

If you install the ColdFusion MX server configuration, or the J2EE Configuration on JRun, and either of the following is true, you cannot have distributed multihomed websites where different websites (such as and use the same ColdFusion MX server:

  • The web servers are on UNIX or Linux and ColdFusion is on Windows.
  • The web servers are on Windows and ColdFusion is on UNIX or Linux.
On WebLogic 8, ColdFusion MX throws a TemplateNotFoundException error rather than displaying a directory listing when trying to load a nonexistent welcome file.

Crystal Reports 9 no longer installs the crpe32.dll file in the C:\Winnt\system32 directory; it installs the file in the C:\Program Files\Common Files\Crystal Decisions\2.0\bin directory. ColdFusion looks for this file in the C:\Winnt\system32 directory. If the wrong version of the crpe32.dll is in theC:\Winnt\system32 directory, users receive the error "An unexpected error occurred while using the Crystal Engine.Error number 525 occurred."

If you use Crystal Reports 9, copy the crpe32.dll file from the C:\Program Files\Common Files\Crystal Decisions\2.0\bin directory to the C:\Winnt\system32 directory.

RDS does not work when the CFIDE/main/ide.cfm page is running behind NTLM security.
ColdFusion MX can return incorrect time values if Windows 2000 Server is set to the "Australia/Sydney" time zone. This problem is due to Sun bug #4762673. To work around this issue, set the user.timezone JVM argument.

Add this to your JVM arguments:

For more information, see
When you run ColdFusion MX J2EE configuration on JRun, you get an error if you request a URL with a trailing slash, such as index.cfm/. To support this URL format, typically referred to as search engine safe (SES), add a *.cfm/* servlet mapping to your jrun_root/servers/server_name/cfusion-ear/cfusion-war/WEB-INF/web.xml file (for example, C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\web.xml). Add the following entry to the file. (If you already have a mapping with an ID of macromedia_mapping_9, change the last character to be one greater than the current highest number.)

<servlet-mapping id="macromedia_mapping_9">

Back to Contents


ColdFusion MX on WebSphere 5: The enctype attribute of a form tag causes double-byte characters in the property values of the form to be set incorrectly in the Form scope. This problem occurs whether the OS locale is English or Japanese. To resolve this problem, remove the enctype parameter from the form tag.
ColdFusion MX does not work on an operating system that is set to the Turkish locale. To work around this problem, set the ColdFusion JVM locale to US by adding the following switches to the java.args line in the jvm.config file:

Back to Contents

Installation and configuration

After you install ColdFusion MX 6.1, if you stop the new services and try to switch back to the old ones, you must manually update several registry entries for SequeLink, because it points to the wrong installation (and hence the wrong data sources). For more information, see TechNote 18800.

Although the ColdFusion MX 6.1 supports RedHat Linux 7.3, 8.0, and 9, the Linux installation must have the corresponding RedHat libc compatibility libraries to run ColdFusion MX on these platforms. At the time of this release, these packages are as follows:

RedHat-9 for i386 compat-libstdc++-7.3-2.96.118.i386.rpm
RedHat-8.0 for i386 compat-libstdc++-7.3-2.96.110.i386.rpm
RedHat-7.3 for i386 compat-libstdc++-6.2-

Users must have a libc of version 6.2-2.x or later for RedHat 7.3, or 7.3-2.x for RedHat 8.0 or 9.

This allows users of these Linux operating systems to use C++ CFXs. Verity is not supported on these platforms.

Deploying ColdFusion MX on an application server using a 1.3.x JVM requires that you rename the WEB-INF/cfusion/lib/tools.jar file or replaced it with the copy that ships with the 1.3.x JVM.
InstallAnywhere requires 256 colors or the installer crashes trying to paint the first screen (an immediate crash or 100% CPU utilization). Users often have servers set to 16 colors, or when going through Terminal Services, many systems use 16 colors. Console mode (text) installation is not available on Windows to avoid this problem.
If you uninstall ColdFusion MX on Windows Server 2003, the C:\CFusionMX\runtime\bin\jrunsvcmsg.dll file remains locked by the OS and cannot be deleted after uninstalling. You must stop the Windows Management Instrumentation service to delete the file.
If your web server runs on a port other than port 80, the installer cannot start the ColdFusion MX Administrator automatically to run the Configuration Wizard.
When you upgrade ColdFusion MX to ColdFusion MX 6.1 on Windows, the Microsoft Access with Unicode driver is not initially included on the ColdFusion MX Administrator Data Sources page drivers option list. To display the option, open the Data Sources page in the ColdFusion MX Administrator, then restart the ColdFusion server.

On UNIX and Linux, if you install the ColdFusion MX server configuration and configure it to use a web server other than the built-in web server, the installer can complete successfully, but the web server connector might not be installed properly. This behavior can occur because on UNIX and Linux, the web server connector configuration utility (wsconfig.jar) does not run until the first time ColdFusion is started, and it can fail silently. An active firewall can cause this problem by blocking the connector configuration utility. To help prevent this issue, ensure that the following ports are free and that the firewall does not block them. These ports must always be available for ColdFusion to use the web server connector.

ColdFusion MX Server:     51010, 2901
ColdFusion MX with JRun: 51020, 2902

Note: If port 2901 or 2902 is not available, the web server connector installer autodetects and configures ColdFusion to use the first free, unblocked port value in the range 2900-3000.

For more information on ColdFusion MX port use, see TechNote 18336.

If you uninstall ColdFusion MX 6.1 on Windows 2003, the Uninstaller can hang after uninstalling ColdFusion, and continues to display the last step, the "Software Database..." step, instead of the Finished screen. If this happens, use the Task Manager to end the Uninstall Macromedia ColdFusion MX process. All uninstallation steps have completed by the time the process hangs, so no additional action is required.
The ColdFusion MX Uninstaller cannot remove the runtime directory that contains the JRE that is installed by ColdFusion. You can manually delete this directory after you uninstall ColdFusion.
When you uninstall the server configuration of ColdFusion MX 6.1, you might get an error message similar to "The uninstall during this iteration failed with the following error: Unable to remove c:\cfusionmx\runtime", and the Uninstaller does not remove the ColdFusion MX directory (for example, C:\CFusionMX). To complete the uninstallation process, manually delete your ColdFusion MX directory.
When updating ColdFusion MX Server to the ColdFusion MX 6.1 server configuration, an error might occur during the updating of the cfdocs directory. If an error happens, the installer logs a message to a cf_root/cfdocs_updater_failed.txt file, but it does not inform you of the problem. (The failure to create the cfdocs directory has only been noted on configurations that use Microsoft IIS as the web server.) If this problem occurs, download the ColdFusion MX 6.1 documentation from the Macromedia website.

If you are upgrading an installation that has RedHat 8 or 9 and the RedHat Stronghold 4 web server, you must add the following switch to the command line for wsconfig.jar to upgrade Stronghold:


Additionally, in many cases, even if you use this switch, you might get an EAPI error in the error.log file on startup. In this case, you must compile your connector from source. Source code and instructions found in cf_root/bin/connectors/src/ in the file.

For more information, see the connector FAQ.

If the ColdFusion JVM classpath has an entry that is escaped with backslashes, as in c:\\temp\\lib, the Updater does not retain the escape characters when it carries over the path, resulting in an incorrect path.
When you upgrade from ColdFusion MX 6.0 to 6.1, the ColdFusion MX Configuration and Settings Migration Wizard might not properly migrate existing ColdFusion Administrator Java JVM Class Path entry backslashes. This can cause data sources of type 'Other' to fail with the error "No suitable driver available for". To prevent this problem, change all backslashes in the Class Path field to forward slashes before you upgrade to ColdFusion MX 6.1, or correct the path in the Administrator after the migration finishes.
On Windows 2003 systems with Service Pack 1 (SP1), the installer immediately exits in the "preparing to install" dialog before extracting files.  This worked previously on Windows 2003 without SP1.

A feature of Windows 2003 Service Pack 1 is "Data Execution Prevention".   This security feature blocks the InstallAnywhere self-extractor for CF 6.1 and all JRun4 Updaters.  (CF 7.0 is not affected).  To fix this problem, do the following:

  1. Click Start, right click My Computer, and select Properties.
  2. On the Advanced tab, click the [Settings] button under the Performance section.
  3. Select the Data Execution Prevention Tab in the Performance Options dialog.
  4. Select the radio button for "Turn on DEP ... except those I select:"
  5. Select "Add" and select the Coldfusion or JRun installer.  (the entry shows up as "InstallAnywhere Self-Extractor" in the dialog)
  6. Select "Apply" on the "performance options" and "OK" on the "System Properties" page
  7. Now run the installer

Here is Microsoft's description of this feature:

Back to Contents


(J2EE Integration) If you include a JSP from within a CFM page using GetPageContext().include("somepage.cfm"), ColdFusion MX does not send the form element data to the JSP page. This problem is specific to J2EE application servers (IBM WebSphere, in particular) that return false for the markSupported() function in their ServletInputStream.
(CFX) Calling a nonexistent C++ CFX procedure or entry point might cause a JVM crash on UNIX.
(cfcompile) To use the cfcompile utility to precompile CFM pages, you must specify both the webroot and the directory that contains the files to compile in the command line. (You can omit the directory to compile the files in the webroot.) You must also ensure that you do not have a pre-1.4.2 JRE in your system path, because it will take precedence over the one assigned to the path assigned in the batch file.

Back to Contents



Deleting all IP restrictions from a sandbox that included such restrictions prevents socket access instead of opening up the access. To work around this problem, delete and recreate the sandbox.


When indexing or searching Verity collections with the cfindex tag with a type="custom" attribute, the Verity collection fails to index or return search results on HP-UX platforms. For more information, see TechNote 18286.
If .pdf is not specified in the "File Extensions" text field of the ColdFusion MX Administrator or in the extensions attribute of the cfindex tag, indexing PDF files created with Acrobat Distiller 4.x or later will cause ColdFusion MX on Solaris to generate a core dump and restart. For more information, see TechNote 18517.
Verity cannot index documents on RedHat Linux versions 7.3 and later.

Back to Contents


When you use the cfwddx tag to convert CFML to WDDX, it fails to properly convert MySQL date fields in a query. To work around this problem, use the MySQL date_format function to create a computed column that returns a pure date without the time component that is normally returned for date columns.

Web services


If you call local components within components that are declared as web services, the mappings set in the ColdFusion MX Administrator are ignored. To work around this problem, create a virtual directory for the folder with the mapping. For example, edit the jrun-web.xml file and create a mapping with the same data as the ColdFusion mapping, such as the following:


Back to Contents

More information about this release

©2003 Macromedia, Inc. All rights reserved.