
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 43
8 Troubleshooting CFML Processing on .NET
When having trouble with execution of CFML pages in BlueDragon.NET, the following tips re-
garding the processing of CFML on the .NET framework may help. Additionally, see a further
discussion of general CFML troubleshooting tips in the BlueDragon 7.1 CFML Compatibility
Guide.
8.1 CFML Pages Do Not Run at All
When CFML pages do not run at all, the following may identify possible solutions.
8.1.1 File Not Found Errors
If you’re trying to browse a CFML page or the BlueDragon Admin, and you get a BlueDragon
File Not Found error (or an ASP.NET resource cannot be found or similar errors),
you should confirm that you’re using the correct URL for IIS to serve the page.
Perhaps the easiest way to avoid mistakes in making requests to CFML (or ASP.NET) pages is
to use the “browse” feature of the IIS Admin interface. First, find your desired website, then the
directory and filename to be browsed. Right-click on the filename and choose Browse. IIS will
launch your browser using the appropriate URL needed to open that file in that given
website/path.
If the path is something very different from what you expected, consider the information in sec-
tions 5.1.1 and9 8.2.
8.1.2 Page Returns Source Code or Does Not Run at All
If the URL is correct but CFML pages simply don’t run, or return the source of the page, one of
the first things to consider is making sure that the .NET Framework is properly configured for
IIS and ASP.NET pages. Since CFML pages are processed in the same pipeline as ASP.NET
pages (see section 2.1.1), if the latter don’t work, the former won’t either.
The simplest way to ensure that the .NET web application is properly configured and running is
to run an a simple ASP.NET page, such as the following (name it test.aspx or similar and
place it in the same directory as your intended CFML):
<%@ Page language="c#" %>
<% Response.Write("test"); %>
If this page fails to runs as expected, this is an indication that the problem is not with BlueDra-
gon but instead with the .NET Framework or the configuration of IIS with the .NET Framework.
See section 2.1 for some common problems in Windows 2003 that may prevent ASP.NET (and
therefore CFML) pages from running. Similarly, the following section explains a common prob-
lem that can make ASP.NET (and CFML) pages not run on IIS.
8.1.2.1 Problems Caused by IIS Being Installed After .NET
If neither ASPX nor CFML pages run, a common problem is when IIS itself is installed (or
reinstalled) after .NET is installed (or reinstalled). The .NET installer normally configures IIS in
Comentarios a estos manuales