ColdFusion 8.01 Broken on Vista SP1 with IIS

I have had several people try this now, and CF8 will not install on Vista SP1 using IIS.

Below is what you get, I could probably manually hack lots of IIS settings and get it working, but since there is nothing on the NET on this, I would like to know why.

I have narrowed it down as I didn't originally know if it was 8.01 related or SP1 related, and it is definately Vista SP1 that breaks everything.

I have reported this to Adobe and they have contacted me asking for more info, so the wheel is in motion. Until then, I don't even have a workaround, mainly because I haven't had the time to work out what config file is missing etc.

Anyway after installing, the configuration page will not open as the connector is not installed properly or not properly configured / connected.

Server Error in Application "DEFAULT WEB SITE"Internet Information Services 7.0Error Summary HTTP Error 404.3 - Not FoundThe 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.Detailed Error Information Module StaticFileModuleNotification ExecuteRequestHandlerHandler StaticFileError Code 0x80070032Requested URL http://127.0.0.1:80/CFIDE/administrator/index.cfmPhysical Path C:\inetpub\wwwroot\CFIDE\administrator\index.cfmLogon Method AnonymousLogon User Anonymous 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: o Ensure that the expected handler for the current page is mapped. o Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. o 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, use the following syntax: %SystemRoot%\windows\system32\inetsrv\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. " 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. Links and More InformationThis 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 »