ColdFusion 9.0.1 Update Now Available

Adobe released update for ColdFusion 9 yesterday. I have installed the update on my server running Windows Server 2008 with IIS 7.

This update now supports running ColdFusion with IIS7 without installing IIS6 Metabase Compatibility. Finally! IIS7 is almost 4 years old!

Download the update from: http://www.adobe.com/support/coldfusion/downloads_updates.html#cf9

Note: If you are running IIS7 with IIS6 Metabase Compatibility, then you'll have to remove IIS6 MC and that will require a restart of the server.

This update is recommended as it includes many bug-fixes and security hot-fixes.

Comments

  1. Tom JenkinsJuly 14, 2010 at 10:34:00 PM GMT+5:30

    Hi there

    I've installed 9.0.1 and am having a few issues with the wsconfig.exe. How do you uninstall IIS6 Metabase Compatibility on windows server 2008??

    No where seems to say :(

    Thanks for the help

    Tom Jenkins

    ReplyDelete
  2. Sameer GuptaJuly 15, 2010 at 4:49:00 AM GMT+5:30

    Tom,

    Please read the post on installing ColdFusion 9.0.1 Update here: http://www.codecurry.com/2010/07/installing-coldfusion-901-update.html

    You can follow from steps 4 to 11 to remove IIS 6 Metabase Compatability.

    -Sameer

    ReplyDelete
  3. larryrampyMarch 20, 2012 at 11:38:00 PM GMT+5:30

    Hello , could you please help me figure out what the issue is?
    I had CF 9.0 running on WIn 2008 R2 64 bit and installed the 9.0.1 update as per the instructions. When I used the CF config tool all my sites went down and was left with a 404 error on all sites.
    I went into the applicationhost.config file after much research and found these entries below.
    The first entry was causing the error when I removed it from the config file all my sites started working again. The error said the path was invalid... but the path was good.
    Here are the handlers I found for CF, also are these the correct ones for 9.0.1? Please help..thanks!

    ReplyDelete
  4. larryrampyMarch 21, 2012 at 12:14:00 AM GMT+5:30

    Please look here for the config file:
    http://www.inetdesign.biz/iis7.5-cf-config.htm

    ReplyDelete
  5. UnknownSeptember 28, 2019 at 4:04:00 AM GMT+5:30

    paito warna china
    data sydney
    datahk
    syair sydney
    syairsgp
    datasgp
    paito warna
    http://warungsgp.com/
    live hk 6d
    live sydney

    ReplyDelete

Post a Comment

Be relevant. Spammers will be banned.

Popular posts from this blog

Installing ColdFusion on IIS 7 + Configure IIS for ColdFusion in Windows Vista and Windows Server 2008

Image
When installing ColdFusion on Vista or on Windows Server 2008 you may receive HTTP 404.3 Error, similar to this one:HTTP Error 404.3 - Not FoundThe page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.Additionally if you run ColdFusion Web Server Configuration Tool, you will see a message saying that IIS components are being installed and could take between 2 to 5 minutes of time.You can resolve this error by making sure that the two required components of IIS are installed on your system. Namely:ISAPI Extensions IIS Metabase and IIS 6 configuration compatibility.
Click to Read Complete Article »

ColdFusion Manual Configuration & Issues with TCP ports 51011, 51010 and 51800 on IIS and Apache

Image
ColdFusion works by configuring your web server (IIS, or Apache) to execute files with known extensions (.cfm, .cfml, .cfc et al) to run as script. And for doing that ColdFusion comes with a small and important tool called “wsconfig”. Problem: At times, regardless of operating system and the web server you are using, the ColdFusion installation will fail to configure web-server due to your network settings or firewall/security settings. When running wsconfig tool, you may encounter errors similar to the following:Could not connect to any JRun/ColdFusion servers on host localhost. Possible causes: Server not running
- Start Macromedia JRun4 or ColdFusion server Server running
- JNDI listen port in jndi.properties blocked by TCP/IP filtering or firewall on server
- host restriction in security.properties blocking communication with server Snapshot above shows one of the common scenario when wsconfig will not configure IIS.Solution: H…
Click to Read Complete Article »