Skip to main content
D
DanP11570598
Known Participant
October 28, 2014
Question

CF10 - Update 14 - 404 Error

  • October 28, 2014
  • 2 replies
  • 2759 views

After installing Update 14 in CF10 I can't reach my CF administrator page (or any .cfm content).  When trying to reach administrator at http://127.0.0.1/CFIDE/administrator/index.cfm the server reports a 404 error. When trying to display other .cfm content, I get a 400 error.

I've used the web connector to remove and reinstall the connector to the IIS server, but that didn't help.

Any ideas?

    This topic has been closed for replies.

    2 replies

    M
    Mike Collins_CF
    Inspiring
    September 1, 2016

    I just took a call with a customer having a similar issue, as soon as they updated to ColdFusion 10 Updater 14 nothing would work and they were getting 404.3 errors.

    The problem turns out to be a duplicate servlet mapping for *.CFM.  It looks like it should be *.Cfm, so we changed it to that and CF was back.

    We found this by stopping the service and then starting CF using the ColdFusion10/cfusion/bat/cfstart command.  You see a Parse error of the web.xml in the output when  CF is starting up.

    The service would start but since the web.xml could not be parsed CF was never deployed as a war and therefore you would not see any logging.

    WolfShade
    WolfShade
    Legend
    October 28, 2014

    What web server are you using in conjunction with CF?  If you're using the built-in web server (TOMCAT), then don't forget to add the port number to the URL.

    Or are you using IIS or Apache?

    ^_^

    D
    DanP11570598Author
    Known Participant
    October 28, 2014

    Using IIS.  One other item I forgot to include in my OP.  Additional error detail indicates Error Code 0x80070002 (from IIS).  This seems to relate to handler mapping in IIS.  Are there supposed to be .cfm handler mappings? 

    WolfShade
    WolfShade
    Legend
    October 28, 2014

    Hopefully someone else can answer that.  I've never used CF with IIS.. it's always been the built-in web server, until recently when I tried setting up Apache on my dev system.

    ^_^

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices