Skip to main content
MIKE SHAVEL_908
MIKE SHAVEL_908
Participating Frequently
March 11, 2015
Answered

updgrade CF9 to CF11

  • March 11, 2015
  • 1 reply
  • 844 views

Hi,

Running Windows server 2008 and CF 9.

I'm trying to update CF9 Standard to CF 11 standard.

I've downloaded the trail version.

I run the installer and then the migration wizard runs.

But after that, the site is still running under CF 9. I know this because if I stop the CF9 process, the site goes down.

There must be some other files I am supposed to modify or move but I can't figure out what they are.

I do notice when I go into IIS 7, there are handlers set up for both CF9 and CF11 -- I can tell this by looking at the file paths to the various handlers.

Where is the 'hook' that ties CF into my web pages? That is what seems to not be working. The 'hook' is tying my web pages into CF9 and not CF11

I've been trying this for about a week now and still no luck. Very frustrating.

Help would be much appreciated.

Thanks
Mike

    This topic has been closed for replies.
    Correct answer Charlie Arehart

    Hi, Mike. The “hook” in CF9 is the wildcard handler mapping which connect “* paths to a jrun dll. The “hook” in CF10 is isapi filter (IIS feature separate from handler mappings) that causes all requests to be passed to a tomcat dll (isapi_redirect.dll). Then both also have handler mappings for cfm, cfc, etc that also pass to the respective DLLs for each engine.

    You have two alternatives to consider:

    - one is that you could try to manually remove all the handler mappings for CF9 and that should do it. But then the problem is you may not look at all the places they exist (which could be at the server and site levels, depending on how you or others before you configured things—and those who try to do it via manually tweaking the IIS config files could also be fail as the info may be in multiple places there.)

    - but the easiest solution, generally, if you’re saying you no longer want to run CF9 with your IIS sites at all, is to the run the CF9 web server configuration tool and use its “remove” option to remove the settings in IIS that are connecting it to CF9. BE sure to right-click and use “run as administrator”.

    That said, if folks HAVE manually tweaked those IIS config files, or HAD previously run the tool (when “adding” sites) without running as admin, then you may find that even doing this removal is not sufficient to get things working, as vestiges of CF9 config lines remain (among the possibly multiple config files, at the server and site levels.)

    It can all get rather messy, especially because the CF9 config tool (and CF installer) did their mods to the config files differently, copying ALL handler mappings from the server level into the site level.

    But give the removal a try. That works I’d say 9 out of 10 times. If you’re in the 10 percentile where it is not enough, I’d say that if the above info is not enough for you to get it fixed, you’d be wise to have someone experienced in this (like myself) work with you remotely to quickly understand and resolve things.

    But if the above is enough to get you going, great.

    /charlie

    1 reply

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity ExpertCorrect answer
    Community Expert
    March 11, 2015

    Hi, Mike. The “hook” in CF9 is the wildcard handler mapping which connect “* paths to a jrun dll. The “hook” in CF10 is isapi filter (IIS feature separate from handler mappings) that causes all requests to be passed to a tomcat dll (isapi_redirect.dll). Then both also have handler mappings for cfm, cfc, etc that also pass to the respective DLLs for each engine.

    You have two alternatives to consider:

    - one is that you could try to manually remove all the handler mappings for CF9 and that should do it. But then the problem is you may not look at all the places they exist (which could be at the server and site levels, depending on how you or others before you configured things—and those who try to do it via manually tweaking the IIS config files could also be fail as the info may be in multiple places there.)

    - but the easiest solution, generally, if you’re saying you no longer want to run CF9 with your IIS sites at all, is to the run the CF9 web server configuration tool and use its “remove” option to remove the settings in IIS that are connecting it to CF9. BE sure to right-click and use “run as administrator”.

    That said, if folks HAVE manually tweaked those IIS config files, or HAD previously run the tool (when “adding” sites) without running as admin, then you may find that even doing this removal is not sufficient to get things working, as vestiges of CF9 config lines remain (among the possibly multiple config files, at the server and site levels.)

    It can all get rather messy, especially because the CF9 config tool (and CF installer) did their mods to the config files differently, copying ALL handler mappings from the server level into the site level.

    But give the removal a try. That works I’d say 9 out of 10 times. If you’re in the 10 percentile where it is not enough, I’d say that if the above info is not enough for you to get it fixed, you’d be wise to have someone experienced in this (like myself) work with you remotely to quickly understand and resolve things.

    But if the above is enough to get you going, great.

    /charlie

    /Charlie (troubleshooter, carehart. org)
    MIKE SHAVEL_908
    MIKE SHAVEL_908Author
    Participating Frequently
    March 11, 2015

    Thanks Charlie!
    I will give your solution a try.

    I'm a programmer and database admin. I maintain a CF site but I wouldn't call myself an expert in it, at least not when we get to this level.

    If this doesn't work and your available, it would be great if you could connect to my server and help me out. It's a test server I'm running on Rackspace as a Cloud Server.
    I'll post back here once I try your solution.

    My last ditch solution was to just rebuild the server from scratch with only CF11 on it and go from there. Hopefully it won't get to that.

    Mike

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    March 11, 2015

    Sure, Mike. That’s indeed why I am able to make a full-time business of providing CF server troubleshooting help. Most people are busy enough with their day jobs (whether as CF devs or non-CF sys admins), so they just can’t spend too much time (or prefer not to) to fully understand problems like this, which can sometimes be rather involved (and involve multiple moving parts, as well as things from different releases which may not be documented in one place).

    I do also share such solutions in the form of answers on forums/lists, blog posts, presentations, and videos. And this (resolving issues with the web server config when transitioning from 9 to 10 or 11) is something I’ve been meaning to blog about but had not. That’s why I went ahead and shared the insights for you here in the meantime.

    If you (or anyone reading this) may be interested in more direct help, you can learn more about my services at the consulting page of carehart.org, including rates, approach satisfaction guarantee, and more. I also list other CF troubleshooting consultants in a category of my cf411 site, at cf411.com/cfconsult.

    Hope all that’s helpful, for you and future readers here, and that you’ll have your problem solved soon, one way or another.

    /charlie

    /Charlie (troubleshooter, carehart. org)
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices