Link to home
Start Free TrialLog in
Avatar of bkpierce
bkpierceFlag for United States of America

asked on

SBS 2008 default website conflicting with SBS Web applications

I have a Windows SBS 2008 Server. I cannot get the default website to start while the SBS web applications site is running. When I try to start the default website it says another site may be using the same port. They both are using port 80 and 443 but port 443 is causing the issue. I tried to edit the bindings on either site and add a host name but it is grayed out on both for port 443.

If I try to change port 443 on either site it says "the certificate associated with this binding is also assigned to another sites binding. Editing this binding will cause HTTPS binding of the other site to be unusable"

In the system log there is an error with event ID 1007 for IIS W3SVC

The World Wide Web Publishing Service (WWW Service) did not register the URL prefix https://*:443/ for site 3. The necessary network binding may already be in use. The site has been disabled. The data field contains the error number.

How can I get both of these sites running at the same time?
Avatar of Tray896
Tray896
Flag of United States of America image

If you need to run 2 websites on port 443 (SSL), you will need to configure them on seperate IP addresses.  The only way you can run them on the same IP is if you are using a wildcards SSL certificate.
So to rememdy this, just add a 2nd IP address to your server.  Go to your 2nd website in IIS, click on bindings, edit the bindings and choose your new IP.  If you are hitting these sites by name, edit DNS so that the URL of your 2nd website points to this new IP.
Avatar of bkpierce

ASKER

Any time I try to change any of the bindings for either site's https (port, IP address, SSL certificate) I am getting an message that it will cause the other site to stop working.
binding.JPG
What about if you just delete the https binding for this site and add a new one?
Delete the https binding for the default site? I cannot, i get that same error message from above if I try to delete the https. I don't want the https to become unusable for the SBS web applications because OWA and RWW are in there and I need them to be available on HTTPS.
ASKER CERTIFIED SOLUTION
Avatar of Tray896
Tray896
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Do you know what the file path is for the file? I'm having a hard time finding it.
It is located at C:\Windows\system32\inetsrv\config
That worked pefectly, thank you for all your help.
Avatar of southray
southray

I have the same issue and i am trying to understand what i need to remove from the applicationhost config file?  What part of the config file do I need to remove?

Here are the two parts where port 443 show up in the config file:

Server\ClientAccess\Autodiscover\help" />
                </application>
                <bindings>
                    <binding protocol="Http" bindingInformation="*:80:Sites" />
                    <binding protocol="http" bindingInformation="*:80:remote.domain.info" />
                    <binding protocol="https" bindingInformation="*:443:" />
                </bindings>




Interface" />
                </application>
                <bindings>
                    <binding protocol="http" bindingInformation="*:80:" />
                    <binding protocol="https" bindingInformation=":443:" />
                </bindings>
            </site>
            <siteDefaults>
                <logFile logFormat="W3C" directory="%SystemDrive%\inetpub\logs\LogFiles" />
                <traceFailedRequestsLogging directory="%SystemDrive%\inetpub\logs\FailedReqLogFiles" />

How can I edit either one of these in order to remove the binding from the default web page?

The issue I had was that the default website had both a port 80 and a port 443 binding and this was clashing with the SBS Web Applications site.

I removed the 443 binding from the config file and did an IIS reset. After that I was able to run both the Default Website and the SBS Web Applications alongside each other.