Specificed directory attribute value could not be created

I've encountered a problem and I'm not sure if it's a bug in CKFinder or a misconfiguration on my part. I'm testing CKFinder 1.4.3 on a Windows Vista machine using ColdFusion 8. If I delete the default folders (Files, Images, Flash) code in config.cfm (see below) and then stop and restart the ColdFusion 8 Application Server service, I get an error when tyring to create new folders based on session variables being passed to config.cfm. The error is "The specificed directory attribute value C:/WebApplications/ckfinder/userfiles/184/ could not be created." The 184 is the value of a session variable being passed to config.cfm to create a new folder. After receiving this error once, I'm able to use CKFinder without problem - it seems to be able to create the folder the second time around. If I use a generic config.cfm and allow the default folders (Files, Images, Flash) to be created, I do not get the error at all when trying to create a new folder based on the same session variable. It seems that the default folders must be present to avoid the error. I tried the following with no luck:

- used the generic config.cfm allowing the default folders (Files, Images, Flash) to be created but then tried to limit the default resource based on a dynamic session variable likes this:
config.defaultResourceTypes = '#SESSION.DocumentReference#';
I still received the "The specificed directory attribute value C:/WebApplications/ckfinder/userfiles/184/ could not be created." error

- used the generic config.cfm allowing the default folders (Files, Images, Flash) to be created but then tried to hide these folders likes this:
config.hideFolders[3] = "Files" ;
config.hideFolders[4] = "Images" ;
config.hideFolders[5] = "Flash" ;
CKFinder didn't hide these folders.

Any ideas as to the source of the problem? My workaround is to create the dynamic folders I need using my own ColdFusion code prior to using CKFinder. Once the folders have been created, CKFinder works without generating the error.

<!---
 ### CKFinder : Configuration File - Basic Instructions

 In a generic usage case, the following tasks must be done to configure
 CKFinder:
    1. Check the baseUrl and baseDir variables.
    2. If available, paste your license key in the "licenseKey" setting.
    3. Create the CheckAuthentication() function that enables CKFinder for authenticated users.

 Other settings may be left with their default values, or used to control
 advanced features of CKFinder.
--->

<cfscript>
// This function must check the user session to be sure that he/she is
// authorized to upload and access files in the File Browser. '
config = structNew();

// This function must check the user session to be sure that he/she is
// authorized to upload and access files in the File Browser. '
function CheckAuthentication()
{
   //WARNING : DO NOT simply return "true". By doing so, you are allowing
   //"anyone" to upload and list the files in your server. You must implement
   //some kind of session validation here. Even something very simple as...

   // return session.IsAuthorized;

   //... where session.IsAuthorized is set to "true" as soon as the
   //user logs in your system.

   return true;
}

config.licenseName = '';
config.licenseKey = '';

/* To make it easy to configure CKFinder, the config.baseUrl and config.baseDir can be used.
 * Those are helper variables used later in this config file.
 *
 * config.baseUrl : the base path used to build the final URL for the resources handled
 * in CKFinder. If empty, the default value (/userfiles/) is used.
 *
 * Examples:
 *    config.baseUrl = 'http://example.com/ckfinder/files/';
 *    config.baseUrl = '/userfiles/';
 */

//ATTENTION: The trailing slash is required.
config.baseUrl = "/ckfinder/userfiles/";

/*
 * config.baseDir : the path to the local directory (in the server) which points to the
 * above config.baseUrl URL. This is the path used by CKFinder to handle the files in
 * the server. Full write permissions must be granted to this directory.
 *
 * Examples:
 *     You may point it to a directory directly:
 *    config.baseDir = '/home/login/public_html/ckfinder/files/';
 *    config.baseDir = 'C:/SiteDir/CKFinder/userfiles/';
 *
 *  Or you may let CKFinder discover the path, based on config.baseUrl:
 *    config.baseDir = APPLICATION.CreateCFC("Utils.FileSystem").resolveUrl(config.baseUrl);
 */

//ATTENTION: The trailing slash is required.
config.baseDir = APPLICATION.CreateCFC("Utils.FileSystem").resolveUrl(config.baseUrl);

/*
 * Thumbnails : thumbnails settings. All thumbnails will end up in the same
 * directory, no matter the resource type.
 */
config.thumbnails = structNew();
config.thumbnails.url = config.baseUrl & '_thumbs';
config.thumbnails.baseDir = config.baseDir & '_thumbs';
config.thumbnails.enabled = true;
config.thumbnails.directAccess = false;
config.thumbnails.maxWidth = 100;
config.thumbnails.maxHeight = 100;
config.thumbnails.quality = 80;

/*
 * set the maximum size of uploaded images
 * if uploaded image is larger, it gets scaled down
 * Set to 0 to disable this feature
 */
config.images.maxWidth = 1600;
config.images.maxHeight = 1200;
config.images.quality = 80;

/*
 * config.roleSessionVar : the session variable name that CKFinder must use to retrieve
 * the "role" of the current user. The "role", can be used in the "AccessControl"
 * settings (bellow in this page).
 *
 * Note: to use session variables, session management must be enabled in Application.cfc.
 * In "core/connector/cfm" there is another Application.cfc file.
 * Assign the correct name of your application there.
 */
config.roleSessionVar = 'CKFinder_UserRole';

/*
 * config.accessControl : used to restrict access or features to specific folders.
 *
 * Many "config.accessControl" entries can be added. All attributes are optional.
 * Subfolders inherit their default settings from their parents' definitions.
 *
 *    - The "role" attribute accepts the special '*' value, which means
 *      "everybody".
 *    - The "resourceType" attribute accepts the special value '*', which
 *      means "all resource types".
 */
config.accessControl = arrayNew(1);

config.accessControl[1] = structNew();
config.accessControl[1].role = '*';
config.accessControl[1].resourceType = '*';
config.accessControl[1].folder = '/';
config.accessControl[1].folderView = true;
config.accessControl[1].folderCreate = false;
config.accessControl[1].folderRename = true;
config.accessControl[1].folderDelete = true;
config.accessControl[1].fileView = true;
config.accessControl[1].fileUpload = true;
config.accessControl[1].fileRename = true;
config.accessControl[1].fileDelete = true;

/*
 * For example, if you want to restrict the upload, rename or delete of files in
 * the "Logos" folder of the resource type "Images", you may uncomment the
 * following definition, leaving the above one:
 *
 * config.accessControl[3] = structNew();
 * config.accessControl[3].role = '*';
 * config.accessControl[3].resourceType = 'Images';
 * config.accessControl[3].folder = '/Logos';
 * config.accessControl[3].fileUpload = false;
 * config.accessControl[3].fileRename = false;
 * config.accessControl[3].fileDelete = false;
 *
 * ResourceType : defines the "resource types" handled in CKFinder. A resource
 * type is nothing more than a way to group files under different paths, each one
 * having different configuration settings.
 *
 * Each resource type name must be unique.
 *
 * When loading CKFinder, the "type" querystring parameter can be used to display
 * a specific type only. If "type" is omitted in the URL, the
 * "DefaultResourceTypes" settings is used (may contain the resource type names
 * separated by a comma). If left empty, all types are loaded.
 *
 * maxSize is defined in bytes, but shorthand notation may be also used.
 * Available options are: G, M, K (case insensitive).
 * 1M equals 1048576 bytes (one Megabyte), 1K equals 1024 bytes (one Kilobyte), 1G equals one Gigabyte.
 * Example:
 *    config.resourceType[1].maxSize = "2M";
 */

config.defaultResourceTypes = '';

config.resourceType = arrayNew(1);

config.resourceType[1] = structNew();
config.resourceType[1].name = '#SESSION.DocumentReference#';
config.resourceType[1].url = config.baseUrl & '#SESSION.MessageID#';
config.resourceType[1].directory = config.baseDir & '#SESSION.MessageID#';
config.resourceType[1].maxSize = '5M';
config.resourceType[1].allowedExtensions = 'pdf';
config.resourceType[1].deniedExtensions = '';

/*
 Due to security issues with Apache modules, it is recommended to leave the
 following setting enabled.

 How does it work? Suppose the following:

   - If "cfm" is on the denied extensions list, a file named foo.cfm cannot be
     uploaded.
   - If "rar" (or any other) extension is allowed, one can upload a file named
     foo.rar.
   - The file foo.cfm.rar has "rar" extension so, in theory, it can be also
     uploaded.

In some conditions Apache can treat the foo.cfm.rar file just like any ColdFusion
script and execute it.

If checkDoubleExtension is enabled, each part of the file name after a dot is
checked, not only the last part. In this way, uploading foo.cfm.rar would be
denied, because "cfm" is on the denied extensions list.
*/

config.checkDoubleExtension = true ;

/*
 * Perform additional checks for image files
 * if set to true, validate image size
 */
config.secureImageUploads = true ;

/*
Indicates that the file size (maxSize) for images must be checked only
after scaling them. Otherwise, it is checked right after uploading.
*/
config.checkSizeAfterScaling = true ;

/* For security, HTML is allowed in the first Kb of data for files having the
 * following extensions only.
 */
config.htmlExtensions = 'html,htm,xml,js' ;

/*
Folders to not display in CKFinder, no matter their location.
No paths are accepted, only the folder name.
The * and ? wildcards are accepted.
*/
config.hideFolders = arrayNew(1);
config.hideFolders[1] = ".svn" ;
config.hideFolders[2] = "CVS" ;

/*
Files to not display in CKFinder, no matter their location.
No paths are accepted, only the file name, including extension.
The * and ? wildcards are accepted.
*/
config.hideFiles = arrayNew(1);
config.hideFiles[1] = ".*" ;

/* Set it to false to disable uploading of the dot files
 * e.g. .htaccess, .ftpquota
 */
config.allowDotFiles = true;

/* Due to known issues with GetTempDirectory function, it is
 * recommended to set this vairiable to a valid directory
 * instead of using the GetTempDirectory function
 */
config.tempDirectory = GetTempDirectory();

/*
 * After file is uploaded, sometimes it is required to change its permissions
 * so that it was possible to access it at the later time.
 * If possible, it is recommended to set more restrictive permissions, like 0755.
 * Set to 0 to disable this feature.
 * Note: not needed on Windows-based servers.
 *
 */
config.chmodFiles = 644;
/*
 * See comments above.
 * Used when creating folders that does not exist.
 */
config.chmodFolders = 755;
</cfscript>