Starting a custom WebSite with https (Port 443) binding you may encounter following problem:
Event viewer says
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix https://localhost:443/ for site 2. The site has been disabled. The data field contains the error number.
The problem is: one of currently running programs uses the port and doesn’t let IIS to start the WebSite. Which program does it .- displays TcpView tool from Sysinternals:
In this case it is Skype: quit it – not just log out etc., you have to quit the Skype process to release the port. Then restart WebSite – and enjoy!
BTW: if you start Skype after the WebSite started – it starts as well and finds another port to communicate: you do not have to restrict you Windows comfort working without Skype while using local IIS WebSite with https binding
7 comments:
Mike I have this problem, it will be nice from you to elaborate on that, mean, how did you know with tcpview? is there one use port 443 I don't see how in all these files...
Louis, do following:
1. download tcpview from
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
2. start tcpview with Administrator privileges
3. search in Output list for a program hanging on port 443
That's what I did the first time and I didn't find a local port with 443...
I don't see my last post, whatsoever my last question was: I didn't see any files with port 443, why?
I restart computer and now IIS restart without any problems. intermittent problem...
ok, so the IIS failed to Register the port on the first try and didn't retry until restart...
Yes, but I look on the events manager and it said at this time something from Microsoft was in upgrading. I think it's the defender... My IIS is the last one and windows 8.1... Thank you very much for your help Mike! I will keep your blog not far...
Post a Comment