5 Replies Latest reply on Nov 20, 2013 5:00 AM by vishu#13

    Can't open cfm pages


      New install of CF10 on IIS7 does not open any cfm pages tries to download instead.

        • 1. Re: Can't open cfm pages
          tribule Level 2

          First try running the connector tool. C:\ColdFusion10\cfusion\runtime\bin\wsconfig.exe. Select "all" when prompted and then OK. Then try CF again.

          • 2. Re: Can't open cfm pages
            TPBrooklyn Level 1

            It was one of the first things I tried. Thanks

            • 3. Re: Can't open cfm pages
              vishu#13 Level 3

              Update CF 10 and then After running the connector tool (as run as admin), check the handler mappings in IIS



              then double click on anyone of them to see, are they pointing to the correct location or not




              You can test the same by creating a Test website in IIS with a test.cfm. Make sure that you have full admin rights on that Test website folder.


              If you are not able to open CF 10 admin, then you can try to run CF 10 admin via it's internal port : http://www.youtube.com/watch?v=iHhSPTmRozM






              • 4. Re: Can't open cfm pages
                Aegis Kleais Level 3

                Usually, when a server attempts to offer a file that is supposed to be executed as a download instead, there is no file extension association for it.  This can be checked in both the handler mappings (where CF-associated file types are pointed to the isapi_redirect.dll file) and in your mime types (ensure that entries for CF-related extensions do NOT exist, or they may be interfering with the rendering process).


                ColdFusion default renders CFM/L pages as text/html unless otherwise specified, so no mime type entries should exist.  (But handlers need to exist, or CF is never handed off the request when someone visits a page)

                • 5. Re: Can't open cfm pages
                  vishu#13 Level 3

                  You can try changing the application pool for your site and then observe the behavior. Like you have test site and default site then there will be 2 pools for each of them i.e test and default app pool. If you are facing issue with default web site then change the app pool of default site to test pool and then test the behavior. It might be the issue with the app pool