Highlighted

Run ColdFusion on IIS Express

New Here ,
Jul 29, 2014

Copy link to clipboard

Copied

I was trying to run ColdFusion on IIS Express. I have used ColdFusion's Web Server Configuration Tool to configure website on IIS. I wanted to configure it for IIS Express.

Views

780

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Run ColdFusion on IIS Express

New Here ,
Jul 29, 2014

Copy link to clipboard

Copied

I was trying to run ColdFusion on IIS Express. I have used ColdFusion's Web Server Configuration Tool to configure website on IIS. I wanted to configure it for IIS Express.

Views

781

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jul 29, 2014 0
Adobe Employee ,
Jul 30, 2014

Copy link to clipboard

Copied

IIS Express works well with ASP.NET and PHP applications (IIS Express Overview : The Official Microsoft IIS Site). ColdFusion is not tested with IIS express so far. You may try to use it and can explore the web/Adobe Forums, in case you face any issue.

Regards,

Anit Kumar

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 30, 2014 0
New Here ,
Jul 30, 2014

Copy link to clipboard

Copied

As I have mentioned, I have used ColdFusion's Web Server Configuration Tool to configure website on IIS. Could you please enumerate the steps that the tool takes to configure IIS for ColdFusion. I know it creates 2 virtual directories (namely CFIDE & Jakarta) and adds handlers to applicationHost.config. I followed the same on IIS Express manually, but couldn't get it working.

Here is the error I am getting:

HTTP Error 404.3 - Not Found

The 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.

Most likely causes:

  • It is possible that a handler mapping is missing. By default, the static file handler processes all content.
  • The feature you are trying to use may not be installed.
  • The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)
  • If ASP.NET is not installed.

Things you can try:

  • In system.webServer/handlers:         
    • Ensure that the expected handler for the current page is mapped.
    • Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
    • Pay extra attention to typographical errors in the expected handler line.
  • Please verify that the feature you are trying to use is installed.
  •            Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.         
    1. To set a MIME type, run the following command in the IIS Express install directory: appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
    2. The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
    3. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']
               Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.       
  • Install ASP.NET.
  • Check the failed request tracing logs for additional information about this error. For more information, click here.

Detailed Error Information:

                    
Module   StaticFileModule
Notification   ExecuteRequestHandler
Handler   StaticFile
Error Code   0x80070032
                  
Requested URL   http://localhost:49248/index.cfm
Physical Path   C:\Users\kbajpai\Documents\Code\DataRequest\datarequest\index.cfm
Logon Method   Anonymous
Logon User   Anonymous
Request Tracing Directory   C:\Users\kbajpai\Documents\IISExpress\TraceLogFiles\DATAREQUEST
 

More Information:

  This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files. 

View more information »

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 30, 2014 0
Adobe Employee ,
Jul 31, 2014

Copy link to clipboard

Copied

The steps to create connectors are IIS manual connector configuration | ColdFusion 10 . It has the details about the files/folders it touch base.

Regards,

Anit Kumar

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jul 31, 2014 1