Thanks for the input - I thought about doing that as well yesterday, so
I made the change today. However, now IIS just serves up the page for
download rather than parsing it with CFMX. I have a feeling I'm SOL
until an update gets released, if one does at all. I'll be using
virtual machines for this stuff I think until then.
Damon wrote:
I do not have Vista and this may be a log shot but you can try to add a MIME
type in IIS (IIS 6 you right click the computer name in the IIS manager and
go to properties, not sure for IIS 7) of .CFM for extension and
cfm-application/octet-stream for mime type. This should at least let IIS
serve up the cfm.
Just a guess
-Damon Ledet
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Staver
Sent: Monday, November 13, 2006 6:41 PM
To: [email protected]
Subject: [ACFUG Discuss] Coldfusion MX 7.0.2 and Windows Vista Enterprise
x86
I'm going to go out on a limb here and assume that nobody has tried this
yet, but I have the final release of Windows Vista Enterprise that was
released to manufacturing running on my workstation now. It's a completely
fresh install, and I attempted to install CFMX 7.0.2 on it to run with IIS
7. As you might assume, it doesn't work. I'm running the
x86 version, rather than the x64 in the hopes more things work with it.
I've been wrong with that guess mostly for a lot of apps.
Below is what IIS spits out:
--------------------------------------------------------------------------
Server Error in Application "Default Web Site"
HTTP Error 404.3 - Not Found
Description: The page you are requesting cannot be served because of the
Multipurpose Internet Mail Extensions (MIME) map policy that is configured
on the Web server. The page you requested has a file name extension that is
not recognized, and is not allowed.
Error Code: 0x80070032
Notification: ExecuteRequestHandler
Module: StaticFileModule
Requested URL: http://127.0.0.1:80/CFIDE/administrator/index.cfm
Physical Path: C:\inetpub\wwwroot\CFIDE\administrator\index.cfm
Logon User: Anonymous
Logon Method: Anonymous
Handler: StaticFile
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.)
What you can try:
* In system.webServer/handlers:
* Ensure that the expected handler for the current page is mapped.
* Pay careful attention to preconditions (e.g. runtimeVersion,
pipelineMode, bitness) and compare them to the settings for your application
pool.
* Pay careful 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. Open a command prompt and change directory to
%windir%\system32\inetsrv.
2. To set a MIME type, use the following syntax: appcmd set config
/section:staticContent /+[fileExtension='string',mimeType='string']
3. The variable fileExtension string is the file name extension
and the variable mimeType string is the file type description.
4. For example, to add a MIME map for a file which has the
extension ".xyz", type the following at the command prompt, and then press
Enter:
5. 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.
* Create a tracing rule to track failed requests for this HTTP status
code. For more information about creating a tracing rule for failed
requests, click here.
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.
Server Version Information: Internet Information Services 7.0.
--------------------------------------------------------------------------
Does anybody have this working by chance? I realize Vista has only been
completed for few days now, but I was just trying to get an early start :)
--
-Mike Staver
[EMAIL PROTECTED]
http://www.fimble.com
-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------
