ColdFusion 8 running on ColdFusion 9 multi-server 64bit

[ascott67]

I am at a loss to figure this out.

Here is the installed sequence.

1) Install ColdFusion 9 mult-server as internal web server, upgrade to 9.01

2) Install ColdFusion 8 as new instance

This means that ColdFuson 8 is running on port 8301, ColdFusion 9 is running on port 8300 this works fine.

The problem I am having is mapping this with the JRun connector to IIS, ColdFusion 9 I have no problems what so ever. But ColdFusion 9 is giving me nothing but troubles no matter what I try.

The error message is

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.

Or if I setup the handler manually for *.cfm I get this

Either the Macromedia application server(s) are unreachable or none of them has a mapping to process this request.

What or how do I get ColdFusion 8 to work? The thing that I have noticed is that the index.cfm is not added to the default documents, and only the jws and jsp handlers are created. My guess is that this is not tested by Adobe and doesn't work.

Can anyone confirm that they have it working in this manner, if so what steps did you do to get it to work?

Thanks in Advance.

[Charlie Arehart]

You don't say, but is this IIS 7? If so, the main problem is that CF8 did not support it. Indeed, neither did CF9, until formal support was added in 9.0.1, which is perhaps why you've had the good result there. To be clear, one could struggle to get CF 8 and 9 to work on IIS 7, but the point is that it's not point and click simple as with CF 9.0.1.

Most important for getting older releases to work is to enable isapi extension and IIS 6 compatibility (again, not needed for 9.0.1). There are various people who have written about trying to get releases prior to 9.0.1 to work with IIS 7. Check out:

http://www.codecurry.com/2009/09/installing-coldfusion-on-iis-7.html

http://blog.kukiel.net/2009/07/installing-coldfusion-8-9-on-vista-and.html

http://dale.fraser.id.au/2008/05/coldfusion-8-vista-sp1-solution.html

The following even talks about it from the CF7 timeframe:

http://www.communitymx.com/content/article.cfm?cid=224AA&print=true

Let us know if that helps.

/charlie

[ascott67]

Charlie,

First I need to explain that I have ColdFusion 8 working on IIS7.0 and IIS7.5 with no problems, I am very well aware that the reason ColdFusion 8 doesn;t work in these versions of IIS is that you need to not only do some of the things you suggested. You also need to setup the IIS6 compatability option as well.

No, the problem is with the JRun connector itself.

I manged to sort this out, but the problem was not what I had thought it would be.

First I had forgotten that the instance (EAR) had actually a context setup, and this was not being used to navigate in anyway shape or form. So when I started using this it all worked well sort of.

But when using the JRun connector to set it up, there is an option to select whether to run this as a ColdFusion 9 application. One is going to make the assumption that if setting up a ColdFusion 8 instance connection to not select this. The proble here is if one doesn't select that option, there is no default document setup for index.cfm, and the cfm files don't work either. No ColdFusion error message are every displayed, so one is not going to know what is going on.

So when I ran the connector, and selected this option for a ColdFusion 8 instance everything started working as expected.

Talk about so non inutitive, but it was a hard lesson learned.

[wc2]

I am experiencing the same dificulties and have followed what I understand to be the same path but I must be missing something. I install CF9 as multiserver and then CF8 as an EAR. From there CFAdmin to create an instance for each server. I can see both versions of CF running and can get to both admins without problems. I am setting context root to / on CF8 install and checking the box for CF9 configuration. It doesn't appear to make any difference on what settings I use as I continue to get the error. Can you elaborate on how you were able to overcome this issue.