I'm getting W3SVC Event ID: 1114 and 1007 on one of my WFE nodes. The other node has the site configured with SSL and it is working fine. Event ID: 1114 is: Description: One of the IP/Port combinations for site '615760742' has already been configured to be used by another program. The other program's SSL configuration will be used. Event ID: 1007 is: Description: Cannot register the URL prefix 'https://*:443/_layouts/inc/' for site '615760742'. The necessary network binding may already be in use. The site has been deactivated. The data field contains the error number. Data: 0000: b7 00 07 80 ·..€ I am also getting a status in IIS of "Cannot create a file when that file already exists". If I remove all SSL confuration from the site on the node with the error message then I am able to browse the site on that node only. The SharePoint farm consists of two NLB WFE nodes an application server holding the Central Admin and a database server.

Is the NLB a 3rd party ? e.g. F5 Can you access the bad node with https://servername/path? The obvious... has anything changed on either and have your tried the good old "iisreset" from a command prompt? Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

The NLB is Windows server software NLB. And yes the iisreset has been performed as well as server reboots many times. No I cannot access the node with https://servername/path. This is a top level site so there is no path. All other sites on the node are working fine as they have for years now. The node that is in error did have a bad sts site template at the time. So the site ended up being created just on one node but not the other. The sts site template was repaired and then the site showed up on the other node as expected. Then SSL was configured and this is where I'm at now with this SSL problem. I can browse the site on the problem node if I remove all SSL configuration. If delete the site from iis on the problem node will it be replicated back to the node from the other WFE?

Please read what follows from http://technet.microsoft.com/en-us/library/cc298636.aspx first: About updating a Web application URL and IIS bindings Unlike typical IIS Web applications, you cannot simply use IIS Manager or other IIS metabase tools to modify the bindings of IIS Web applications that have been extended with Windows SharePoint Services 3.0. If you modify the IIS bindings of a Web application by adding a host header binding or an SSL port, or by changing a port number, Windows SharePoint Services 3.0 is not aware of these changes and does not update the Web application's alternate access mapping URLs. If you update the Web application's alternate access mappings to change a host header, switch to an SSL URL, or change a port number, Windows SharePoint Services 3.0 will not automatically update your IIS bindings to match. To update the URL or IIS bindings of a Web application, you must unextend and re-extend the Web application, and reconfigure alternate access mapping URLs or IIS Web site bindings. Note: To assign an IP address to an IIS Web site that has been extended with Windows SharePoint Services 3.0, you can directly modify the IIS bindings of an IIS Web site. For more information about this exception, see Microsoft Knowledge Base article 927376: Error message when you try to create a Windows SharePoint Services 3.0 Web application in SharePoint 3.0 Central Administration: The IIS Web Site you have selected is in use by SharePoint. (http://go.microsoft.com/fwlink/?LinkId=110481&clcid=0x409). We do not recommend reusing the same IIS Web site for your HTTP and SSL hosting. Instead, extend a dedicated HTTP and a dedicated SSL Web site, each assigned to its own alternate access mapping zone and URLs. And then, take a look at this blog http://blogs.msdn.com/jjameson/archive/2009/11/09/configuring-ssl-on-sharepoint-sites.aspx And according to http://blogs.msdn.com/joelo/archive/2007/01/02/relationship-between-the-iis-metabase-and-sharepoint-configuration-database.aspx, when you stop the SharePoint Web Application service, SharePoint will delete those IIS Web sites from the server. When you then start the SharePoint Web Application service again, SharePoint will recreate those IIS Web sites based on the settings that SharePoint was originally aware of. (Those stored in the config db.) So, you have to restore the IIS metabase to apply the changes to the bindings, certificate assignments, etc., that you made in IIS Manager. Could you please let us know your steps to configure the SSL which may be the cause of the error message? Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

What about the current situation? Is it OK now?

Thank you GuYuming for your response. I just finally got time to take a look at this issue again and will be applying your suggestions in the next couple of days. I will let you know how it went.