If you get an error like this:

The service could not bind instance 1. The data is the error code.
For additional information specific to this message please visit the Microsoft Online Support site

From W3SVC – then you may have experienced a problem that I ran into today (or something similar).

Basically, if your default web site cannot start, and you are receving this error – apparently it means that it cannot bind a socket to the port you have specified it to run on. So check that you have no applications or services running that are hogging this port (generally 80).
The application that was doing it to me, was Skype. To fix it, you can open skypes options/settings and click on the ‘connection’ section. You will notice that it says ‘use port 80 and 443 as alternatives for incoming connections’ – if you uncheck this, save your settings (no need to restart anything) you should now be able to start your web site again.

Skype does this, so that if there’s a local firewall that’s doing some fancy port blocking, it knows that generally 80 will be open, so it opts to use that when all else fails – but can be very annoying in situations such as these, when you are running a web server on the same box!

Happy configuration!

About cosier

Matthew Cosier is the Chief Technology Officer at Hazaa. We are a group of experienced consultants based in Melbourne, Australia who solve business problems using Microsoft Technology. For more information, please visit http://www.hazaa.com.au

62 responses »

  1. Dylan Parry says:

    Thanks for the useful tips in this article. I suddenly found this problem after cleaning my registry, so I panicked and thought that I had done something wrong! Sure enough though, I shut down Skype and the problem disappeared!

  2. Joe says:

    Thanks for posting this. After looking around at Microsoft, I had almost resigned myself to doing a metabase edit to fix this. Luckily, I took one last shot with Google and found this entry. Skype was the problem.

  3. Mandy says:

    Thanks for this article. I had spent about 1 1/2 trying to fix this and when I read your article, I knew it was the answer – and sure enough it was!

  4. Matthew Cosier says:

    No problems all 🙂
    Glad it was of some help to you all.

    Regards,

  5. Lisa says:

    Thank you so much Matthew!! This was bugging me for ages. Bloody Skype!!

  6. Matthew Cosier says:

    No problems!
    I’m glad it helped yet another poor innocent victem!

    Cheers,

  7. Anonymous says:

    thanks!
    i just installed scype today, then promptly went to work on some web projects and couldnt get anything going! your blog fixed me up immediately.

    josh@pipeline.com

  8. CY says:

    THANKYOU THANKYOU and THANKYOU again, you’ve just dug me out of a deep deep hole.

    Cheers

    Chris

  9. MannyG says:

    I got the same problem just tonight. Thanks a lot for this post.

  10. Neeraj Kesarwani says:

    Thanks for this useful tips.. It resolved my problem

  11. Rob Mello says:

    Your post saved me lots of time. Thanks!

  12. Anonymous says:

    Thanks for the help on this. Was running into a dead end and didn’t know what else to try. Now I can get back to work (I guess that is kind of a good and bad thing).

    Thanks!

  13. Hugo Burm says:

    Thanks.

    You saved me a lot of time. Just like ‘Joe’, I tried Microsoft and I was almost going to hack the metabase. But Skype was the problem.

  14. annesh says:

    Thanks man, it was skype. Awesome, saved me from reinstalling IIS. Ta
    Annesh (23 Aug 2006)

  15. Pradeep says:

    Thanks for your info Mathew, I was able to google you n fix the problem in 2 mins. Excellent tip. Keep up your good work

  16. Paul S says:

    Thanks Matthew – one look in the event viewer – one search on google – found your Blog at the top of the list and my IIS is working again… happy days:)

  17. Doogal Bell says:

    You da man! Odd though, Skype and IIS have been happily playing together for months until this morning.

  18. Anonymous says:

    Number one rank on Google 🙂

    Exactly the right answer.

    Thanks.

  19. Anonymous says:

    Thank you, thank you, thank you! Thank you for posting this answer. I could have pulled my hair out for days on this on.

  20. David Givoni says:

    Thanks, this worked for me too.
    And as the previos poster said, I´ve had Skype and IIS working together for a loooong time without problems. Strange…

  21. Anonymous says:

    Thanks for posting this info. I was getting ready to re-install Windows to get my web server working again. I’ve had Skype and IIS running together for a while now, so never suspected this at all.

  22. Aviad says:

    Thanks very much for your helpful tips.
    It solved my problem – it was also because of skype

  23. Anonymous says:

    Great. Good work, I agree could have kept me puzzled for a long time. Whats more the link from the event log to the MS help site doesnt bring up anything useful ofcourse, but a cutnpaste of the err into google brings a result (this page) as #1 serp. What does that say about Google v MS?

  24. Anonymous says:

    Thank You,

    Your description of the problem and the corresponding solution was very helpful.

  25. Chris says:

    Thanks, I just remembered Skype will hog port 80 and 443.

    Net to setup my router to forward a specific port to my PC.

    cheers, Chris.

  26. Anonymous says:

    Thanks: Outstanding job. I totally forgot about Skype “nailing” Port 80. Yours, Arik Friedman.

  27. JF says:

    Thanks for pôsting this! You just saved me quite a bit of timeof research.

  28. Todd Davis says:

    Thank you, thank you, thank you, thank you, thank you, thank you, thank you, thank you….

    Saved my tush big-time!

  29. Anonymous says:

    GAAH! You just saved me hours of head scratching. Saw that port 80 was giving me binary garbage on a telnet connection, but even netstat couldn’t tell me the program responsible. Thank you VERY much.

  30. Anonymous says:

    Cheers, a quick “I’m feeling lucky” google and this has solved my problem.

    Thanks for the article.

  31. Anonymous says:

    Thankyou, this solved my problem!

  32. Anonymous says:

    Wonderful, though I must say as soon as I got the error, I searched Google, so I didn’t waste much time 😉 It sure seems quite odd for Skype to use port 80 if the default one is not available. And even more odd is why the problem does not occur every day when both the IIS and Skype are automatically starting on booting up the PC. Anyways, thanks a lot for the tip.

  33. Anonymous says:

    Hey mister. This has helped save alot of wasted hours. Thanks again
    Mickey

  34. Anonymous says:

    Thanks for posting this tip. You have fixed my problem! Proof that the internet is truly a global knowledge source!

  35. Anonymous says:

    Thanks for this useful tips.. .All the best I know.
    my progect here:
    porno video

  36. Anonymous says:

    Sir!

    You have saved me a lot of grief this evening! Sure enough it was Skype.

    I have no clue why suddenly this became an issue as I have been running IIS 5 and Skype for over a year on my development machine. And suddenly this evening it rears it’s ugly head!
    Thanks for posting this solution, you are helping save the world!

    Bob from i2bGlobal.com

  37. Anonymous says:

    You’re a lifesaver!
    thanks

  38. garry oliver says:

    Cool – thanks
    restarted with IIS website stopped – could not restart until quit skype – could restart skpe fine after getting IIS site going

  39. Steve says:

    that fixed it! thanks for the post!

  40. tom says:

    same issue different cause. Thanks for the fix. had another app on the same port.

  41. Godsend!! thank you.

  42. Sander says:

    Awesome! Unchecked the box in skype, restarted (Skype said I had to) and sure enough, IIS now starts. Got to love the cryptic, completely useless error from IIS. How about saying something like “can’t bind to socket on port 80”, eh? Not to mention Skype should keep its hands of standard ports by default. They probably added port 80 to bypass firewalls and all that but it should not grab any standard ports unless told to do so. Thanks again!

  43. tikbum says:

    Great tip. straight to the point. Got damn it, Skype!!!

  44. Sunita says:

    This was of great help. Before this i was not able to work on skype and iis together, so if had to talk to somebody, i first had to stop iis “stop my work 😦 “. But not both run together. THANKS!!!

  45. Robin Withey says:

    Spot on! I’d just installed a Skype update, which I guess caused the firewall to block it, so it switched to port 80.

    Thanks!

  46. Daima says:

    Thank You again for this post and for high relevance in google 🙂

  47. phang says:

    Thks…
    This is really a small trick, but save my 2 hours time on reinstall the IIS…

  48. erich says:

    Thanks much, you saved me a good amount of time poking around for what was using port 80 😉

  49. Ervin says:

    Thanks. I solved my problem.

  50. sadaf says:

    I don’t have skype installed and still getting this error. I check port 80 in tcp view and no one is using it. It was working fine and stopped suddenly. If I change the port, it works fine.

  51. Tomasz says:

    You are the star 🙂 Thanks.

  52. jaiganesh srinivasan says:

    three cheers to you !!! you saved my day !!

  53. bp says:

    Thanks for taking the time to post this!

  54. David says:

    Thanks for this entry, I’ve been experiencing all manner of minor issues having just installed windows on my new workstation. I’ve a few more to iron out, (including getting the CTRL+ALT+DELETE logon screen to appear) but this was one I managed to solve with just 3 clicks through Google thanks to this really straight-to-the-point article.

    Thanks again, you’ve saved me a load of extra stress.

  55. Gopan says:

    Thank You very much

  56. Excellent site, keep up the good work

  57. I don’t usually reply to posts but I will in this case, great info…I will add a backlink and bookmark your site. Keep up the good work!

    I’m Out! 🙂

  58. Rahul says:

    Thank you for the help. I have been finding solution for this problem since 2 days. Its a really nice post.
    Thanks once again.

  59. Trupti says:

    Thanks…

  60. Reid says:

    THANK YOU!! saved me a lot of time!

  61. Harry says:

    Thank You

Leave a comment