Stopped sites causing conflicts?RSS

3 replies

Last post Jul 13, 2006 06:08 PM by ericdeily

  • Stopped sites causing conflicts?

    Jul 05, 2006 03:44 PM|mdowney|LINK

    I have a Windows 2003 server running IIS 6 with several additional IP's which each serve a separate web site. Each IP/site combination has not only the normal, running web site with the relevant application code, but also a stopped site on the same IP/port as a "maintenance page". The idea here is that during a failure of a dependent system, the web site could be stopped and the "maintenance" site started in its place.

    Recently, I noticed some strange behavior after issuing an IISRESET command with the "live" sites running. The stopped sites appeared to bind themselves to the sockets in question before the started "live" sites. When it came time for the live sites to start, the following messages were logged in the System Event Log:

    One of the IP/Port combinations for site '144935731' has already be configured to be used by another site.  The other site's SSL configuration will be used.

    Cannot register the URL prefix '' for site '1050148382'. The necessary network binding may already be in use. The site has been deactivated.  The data field contains the error number.

    This suggests that the stopped sites are not fully disabled. When the sites came back up, in this case, the SSL port of the "live" site was not functional ... clearly, not a good thing.

    Any ideas how to prevent this problem? Searching has to this point been futile.

  • Re: Stopped sites causing conflicts?

    Jul 06, 2006 05:41 AM|Christian Paparelli|LINK


    the problem is that you cannot bind to web site with the same ip/port and the error is documented on your post "the web stie 144935731 have the same ip/port of the web site 1050148382" so you have 2 solutions:

    1° change ip or port for the web site 144935731 and use a unused ip or port

    2° use host header

    I suggest to use limited ip number (1 is enough) and use host heder take a look here;en-us;308163

    Christian Paparelli
    [Microsoft MVP Window Server - IIS]
    My job:
    My blog:
  • Re: Stopped sites causing conflicts?

    Jul 06, 2006 05:44 PM|thomad|LINK


    I assume you just stopped the site but didn't change the ServerAutoStart property. Every site is started automatically after an IISRESET if you don't set ServerAutoStart to false.

    Here is how you do it:
    Check if ServerAutoStart is enabled for the default site:
    \Inetpub\AdminScripts\adsutil get w3svc/1/ServerAutoStart

    Set default site to not start automatically:
    \Inetpub\AdminScripts\adsutil set w3svc/1/ServerAutoStart false

    Hope this helps.

    Thomas Deml
    Group Program Manager
    Internet Information Services
    Microsoft Corp.
  • Re: Stopped sites causing conflicts?

    Jul 13, 2006 06:08 PM|ericdeily|LINK

    one thing you can do as well is to take a look at what's registered in HTTP.sys as well by using their HTTPCFG.exe tool.  Examples on usage can be obtained on Technet at

    and to be clear on Thomas' post -> sites are restarted if ServerAutoStart = 1 (true) when you restart the W3SVC (which IISRESET happens to be able to do). 

    Program Manager - IIS
    Release/Proj Mgmt & Support/Health/Instr/Tracing/Logging