Skip to main content
Inspiring
June 5, 2006
質問

How to configure CF on a 64 bit server

  • June 5, 2006
  • 返信数 2.
  • 599 ビュー
I am trying to setup CF MX 7 on our new 64 bit Windows 2003 server (IIS 6). When we ran HTML and ASP pages prior to installing CF, it worked fine. After installing CF we kept getting 500 errors and even HTML/ASP wouldn't work.

After uninstalling CF, it went back to working fine.

I looked up the issue on MS's website, and their explanation states that a 64 bit OS is pre-defined to only allow 64 bit extensions to run; but you can run 32 bit extensions if you configure certain settings to allow it.

Unfortunately, as per MS's usual finesse, they neglect to tell you how to adjust the server to allow 32 bit extensions.

Has anyone here set up their 64 bit server for CF yet? If so, can you give me an idea on how to reconfigure the server so 32 bit extensions will work?

Thx in advance.


    このトピックへの返信は締め切られました。

    返信数 2

    SafariTECH作成者
    Inspiring
    June 10, 2006
    Hmm, I did that, and it altered the IIS server, but now it says service unavailable and the App Pools are throwing errors right left and center; and IIS says it cannot load all extensions.

    All extensions in IIS are currently set to "prohibited", so I'm kind of at a loss as to what to do next so my server can run CF? I really do not want to run a 32 bit OS and lose the great advantages of the 64 bit abilities and architecture.

    I turned the setting you provided back to false and it is back to working ok so long as CF is not installed.
    Participant
    April 20, 2007
    The problem "service unavailable" is caused by the IIS software, when switching the Enable32Bit thing on, the default ASP.NET software/plugin is not allright anymore.

    Microsoft Tech Note

    Just remove the ASP isapi filter on the general properties of your IIS, and things work.
    (We don't need the ASP application layer, if you have the powerful ColdFusion AL installed on your server ;-)
    Participating Frequently
    June 7, 2006
    It's actually IIS6 (on64 bit platform) that requires 64 bit extensions.

    The way to enable 32 communication is to:
    * head to the %systemdrive%\Inetpub\AdminScripts
    * cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true
    * hit Return.

    Andy