Skip to main content
csgaraglino
Known Participant
December 14, 2010
Question

CF8 on Win03 - Blewup IIS?

  • December 14, 2010
  • 2 replies
  • 3317 views

When installing CF8 on Windows 2003 II6 (32bit) this morning I lost IIS? It would no longer serve even HTML pages.

    This topic has been closed for replies.

    2 replies

    csgaraglino
    Known Participant
    December 15, 2010

    So I think I have figured out what the problem, I just don't know how to fix it it.

    The issue seems to be in the W3 Service not being able to stop during the installation.

    I cannot manually stop it either - it just hangs?

    This may be residule form the Win2k to 2003 upgrade?

    Community Expert
    December 15, 2010

    Maybe you can stop it before you do the install.

    Dave Watts, CTO, Fig Leaf Software

    http://www.figleaf.com/

    http://training.figleaf.com/

    Read this before you post:

    http://forums.adobe.com/thread/607238

    Dave Watts, Eidolon LLC
    csgaraglino
    Known Participant
    December 15, 2010

    I tried mannually stopping it and it just hangs. The hosting company that provides the software (they did the OS upgrade) is looking into it now to see what the issue with W3S is. Hopefully they can figure it out?

    Charlie Arehart
    Community Expert
    Community Expert
    December 14, 2010

    We need more information to really help, but here are some things to check:

    - are the web sites "stopped" in the IIS interface, perhaps? You can see the word "stopped" to the right of them in the interface, and right-click to start.

    - how many web sites do you have (as shown in the IIS interface)? Are requests to all of them failing?

    - and are requests for all types of files failing? (htm, cfm, jpg, etc)

    - are you sure you're using the URL that IIS expects? Sometimes what you expect should work is not what it expects should work. Here's a trick: try drilling into a web site, into the directories and file names, and right-click one to choose "browse". That causes IIS to open the file at what it thinks to be the URL for that site. If that works, maybe you were using something else, and then need to reconcile that.

    - is the whole IIS server stopped, perhaps? If you view it in Windows services (world wide web service), is it running?

    - if you restart IIS, does it help (sometimes, installing software that changes IIS requires it to be restarted). Right-click on the server name in IIS, choose all tasks>restart IIS

    - you can also check the windows event logs (Start>Control Panel>Admin Tools>Event Viewer) to view the "system log", to see if there are any messages for the W3SVC source (messages from IIS).

    That's at least a few things to start with. Let us know how it goes.

    /charlie arehart

    charlie@carehart.org

    Providing CF and CFBuilder troubleshooting services

    at http://www.carehart.org/consulting

    /Charlie (troubleshooter, carehart. org)
    csgaraglino
    Known Participant
    December 14, 2010

    - Only 3 are set to stopped and these are deliberate - the rest are running. - There are 53 websites running - yes, html and cfm are faining - yes - no, but I will say this - when I tried to stop the WWWPS service it system could mot on the first try. It hung with a "stopping" status. I then had to stop IIS Admin Service, which in turn stopped the WWWPS - no, see above - I did not see anything in there that was cause for concern? I have sense restored this system back to last night (This is a VMWare snapshot) and I will be attempting this again in the morning - but I am not comfortable not knowing what happened?

    Charlie Arehart
    Community Expert
    Community Expert
    December 14, 2010

    @csgaraglino, I just have to say that you've made it hard for people to appreciate what points you're responding to. Please help us help you. I had to go back and find my message to piece together what responses went with what questions. Even then, it's not clear: are you saying all requests for all file types fail on all web sites? That would seem quite odd. What's the exact failure message?

    That said, there is a "wildcard mapping" that's added to either the root ("web sites") or specific sites, whichever you told the CF installer or web server config tool to connect to CF (all sites, or selected sites). You may want to check that the path for that is correct for wherever CF is installed on your box. Also, have you restarted CF after installing it? It does tell you to do so. That may be all that's wrong.

    If not, let us know more as you learn it.

    /charlie

    /Charlie (troubleshooter, carehart. org)