The service could not bind instance 1.

20 05 2005

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!


Actions

Information

57 responses

8 07 2005
Dylan Parry

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!

12 07 2005
Joe

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.

19 10 2005
Mandy

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!

19 10 2005
Matthew Cosier

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

Regards,

2 01 2006
Lisa

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

2 01 2006
Matthew Cosier

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

Cheers,

10 02 2006
Anonymous

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

5 06 2006
CY

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

Cheers

Chris

10 06 2006
MannyG

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

22 06 2006
Neeraj Kesarwani

Thanks for this useful tips.. It resolved my problem

20 07 2006
Rob Mello

Your post saved me lots of time. Thanks!

21 07 2006
Anonymous

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!

14 08 2006
Hugo Burm

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.

23 08 2006
annesh

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

6 09 2006
Pradeep

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

7 09 2006
Paul S

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:)

18 09 2006
Doogal Bell

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

21 09 2006
Anonymous

Number one rank on Google :)

Exactly the right answer.

Thanks.

3 10 2006
Anonymous

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

4 10 2006
David Givoni

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…

5 10 2006
Anonymous

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.

16 11 2006
Aviad

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

24 11 2006
Anonymous

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?

12 12 2006
Anonymous

Thank You,

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

17 12 2006
Chris

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.

7 01 2007
Anonymous

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

17 01 2007
JF

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

23 01 2007
Todd Davis

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

Saved my tush big-time!

15 02 2007
Anonymous

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.

6 03 2007
Anonymous

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

Thanks for the article.

15 03 2007
Anonymous

Thankyou, this solved my problem!

20 03 2007
Anonymous

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.

19 04 2007
Anonymous

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

30 04 2007
Anonymous

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

5 05 2007
Anonymous

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

10 06 2007
Anonymous

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

27 06 2007
Anonymous

You’re a lifesaver!
thanks

24 08 2007
garry oliver

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

3 09 2007
Steve

that fixed it! thanks for the post!

18 09 2007
tom

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

26 10 2007
neal kernohan

Godsend!! thank you.

9 11 2007
Sander

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!

14 11 2007
tikbum

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

31 01 2008
Sunita

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!!!

8 02 2008
Robin Withey

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!

24 03 2008
Daima

Thank You again for this post and for high relevance in google :)

9 04 2008
phang

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

15 06 2008
erich

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

1 07 2008
Ervin

Thanks. I solved my problem.

21 07 2008
sadaf

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.

15 08 2008
Tomasz

You are the star :) Thanks.

20 09 2008
jaiganesh srinivasan

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

20 09 2008
“The service could not bind instance 1. The data is the error code.” | Mattias Geniar

[...] The service could not bind instance 1. – Skype Issue [...]

9 10 2008
bp

Thanks for taking the time to post this!

16 10 2008
David

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.

21 04 2009
Gopan

Thank You very much

3 09 2009
Bill Bartmann

Excellent site, keep up the good work

Leave a comment