I’ve run into this twice in as many weeks, on Windows 2008 when running the ColdFusion 9.0.1 updater it will fail to complete successfully. Â Each time failing with the same message in the install log:
ANT Script Error:
Additional Notes: ERROR - cfmx-patch-move-files-all.xmlFailed to copy C:ColdFusion9libcfperfmon_9.dll to C:Windowssystem32cfperfmon_9.dll due to C:Windowssystem32cfperfmon_9.dll (The process cannot access the file because it is being used by another process)
Each time, however, I was able to simply rename the dll while ColdFusion was stopped and the upgrade continues successfully.
Recently did an upgrade to ColdFusion 9 from ColdFusion 8 for a customer and ran into an issue with ColdFusion failing to restart after I was done importing the .car file I had created. Â In the coldfusion-out.log file I was seeing the following entry:
Error: no known VMs. (check for corrupt jvm.cfg file)
Checking out the jvm.config file, I realized that I’d imported the old JVM path that referenced ColdFusion 8 (and no longer existed), updating to the ColdFusion 9 path allowed ColdFusion to start correctly.
A few weeks ago I had to assist with migrating a customer with a large amount of Access databases (over 60) to a new server. Â Turns out their new server was completely 64-bit (Windows and ColdFusion) and I didn’t find out about the Access databases until after the server was completely deployed. Â Had I been involved earlier I would have put a stop to that. Â However, I had to make Access play nice with ColdFusion, here’s how I did that.
The first step is to open the 32-bit ODBC Datasource manager in Windows, on this server it was atÂ C:\windows\SysWOW64\odbcad32.exe, where I had to add a system DSN for each Access DSN I was configuring.
As you can see there are a large amount of System DSNs for each database, we’ll be setting up the DSN named ‘blank’ in this post.
After you have a System DSN created for each DSN you need in ColdFusion, you can start adding them to ColdFusion. Â As you can see in the image below we set the data source up exactly as we did in the Windows ODBC manager, same name and path.
Now, when you hit Submit you’re going to get a very ugly error:
Unable to update the NT registry.
Variable DRIVERPATH is undefined.
Don’t fear, the data source is now available for ColdFusion to use. Â Now, why didn’t I just use an ODBC socket? Â Well, you simply can’t – when you go to create an ODBC socket in the ColdFusion Administrator it generates a drop down of 64-bit System DSNs and won’t show you the 32-bit Access DSNs (see the Additional Reading section).
Remember, you’re milage will vary on this and you should be converting those Access databases over to SQL Server or MySQL 🙂
Why my 32 bit applications cannot see the ODBC DSNs that I created on my 64 bit machine ?
Ran into an issue recently with a customer who’s upgrade to ColdFusion 9 caused the Migration Wizard to freeze up when you opened the ColdFusion Administrator for the first time. Â Turns out, you can disable this very simply with the following code taking advantage of the ColdFusion Admin API:
<cfset cfadminob = createObject("component","cfide.adminapi.administrator").login("password") >
Alternately, you could re-enable the wizard by setting all these values to “Yes”, I’ve seen a few installs that don’t have the wizard enabled.
With the release of IIS 7.5 (available in Windows Server 2008 R2 and Windows 7), FTP is finally re-integrated into the main IIS Manager.Â Those of you still using 7.0 know that you need to use the IIS 6 Manager to manage FTP sites.Â One of the great new features in IIS 7.5 FTP is the ability to setup virtual hosts for FTP (multiple FTP sites on port 21 with the same IP) similar to how you would setup web sites with host headers in IIS.Â One of the trip ups when you attempt to log in to FTP is the user name needs to include the virtual host name.Â Consider the following setup:
Notice that one of the bindings is ftp:192.168.1.101:21:cfbeam.localhost, when you actually connect with an FTP client the username needs to be entered as:
Notice the pipe (|) between the virtual host and the user name.Â Assuming you don’t put that in, you’ll likely see the following in the IIS FTP logs and in your FTP client:
Response:Â Â Â 220 Microsoft FTP Service
Command:Â Â Â USER brent
Response:Â Â Â 530-Valid hostname is expected.
Response:Â Â Â Â Win32 error:Â Â No such host is known.
Response:Â Â Â Â Error details: Hostname didn’t match any configured ftp site.
Response:Â Â Â 530 End
Error:Â Â Â Could not connect to server
For more information on configuring virtual hosts in IIS 7.5 see http://learn.iis.net/page.aspx/320/using-ftp-virtual-host-names/
Just had an issue where ColdFusion would only serve a few requests before locking up and sending constant 503 errors.Â Turns out there were almost 200k files in C:Coldfusion8
untimeserverscoldfusionSERVER-INF empwwwroot-tmp.Â So, to fix this I stopped ColdFusion, renamed wwwroot-tmp to wwwroot-tmp2 and make a new wwwroot-tmp.Â Once ColdFusion was started it ran like a champ again.Â My theory is the disk I/O was killing CF when it was looking for a chached file.