Thursday, May 19, 2005

The service could not bind instance 1.

This entry has been moved, Please Click Here to View

37 comments:

Anonymous said...

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!

Matthew Cosier said...

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

Regards,

Lisa said...

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

Matthew Cosier said...

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

Cheers,

Anonymous said...

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

CY said...

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

Cheers

Chris

Anonymous said...

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

Anonymous said...

Thanks for this useful tips.. It resolved my problem

Anonymous said...

Your post saved me lots of time. Thanks!

Anonymous said...

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!

Anonymous said...

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.

Anonymous said...

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

Unknown said...

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

Anonymous said...

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

Doogal said...

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

Anonymous said...

Number one rank on Google :)

Exactly the right answer.

Thanks.

Anonymous said...

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

Anonymous said...

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

Anonymous said...

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.

Anonymous said...

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

Anonymous said...

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?

Anonymous said...

Thank You,

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

Anonymous said...

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.

Anonymous said...

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

Anonymous said...

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

Anonymous said...

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

Saved my tush big-time!

Anonymous said...

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.

Anonymous said...

Cheers, a quick "I'm feeling lucky" google and this has solved my problem.

Thanks for the article.

Anonymous said...

Thankyou, this solved my problem!

Anonymous said...

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.

Anonymous said...

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

Anonymous said...

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

Anonymous said...

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

Anonymous said...

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

Anonymous said...

You're a lifesaver!
thanks

Anonymous said...

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

Anonymous said...

FDA-approved prescription drugs. online pharmacy is the perfect resource for people, largest OnLine Pharmacy and Health information