Tue 19 Jan 2021
Fancy tricks with REST API - Part 1
Mon 11 Jan 2021
Wed 6 Jan 2021
REST plus RPC: the right data in the right format, and no more
Solution to 'Cannot bind port 80' error caused by AVG
Mon 25 May 2009, 09:42 PMTweet
by Ben Langhinrichs
Copyright © 2009 Genii Software Ltd.
What has been said:
817.1. Ulrich Krause (26.05.2009 05:39)
This seems to be a common problem with all Anti Virus Programs. I had the same issue with Eset NOD32.
Instead of removing port 80 from the scan list, I temporarily disable the web scan and after the HTTP task has started, I enable this option again.
Seems to be a more secure way of working around the issue than generally disable any scan on port 80.
817.2. Andreas Rosen (29.05.2009 09:46)
I had a simular problem with the newer Skype using now by default also port 80. I did not get the error during start of Http - I just did not get any answer from the local domino server via http.
solution: stop skype during test - or change the skype configuration
817.3. Scott Marchione (10/20/2010 04:53 PM)
I know this is quite old, but I just ran across this issue myself, however my scenerio seems to be different than what has been outlined here. In my case it seems that IIS running on the 2003 server grabbed port 80 and would not allow HTTP to use it. My work around was to stop the IIS service from starting reload http.
817.4. Narender Mohan (06/15/2011 02:13 PM)
Thanks allot for the such valuable information.
817.5. Prasad KM (06/28/2011 10:21 AM)
Thanks for your Advise.
I was struggling to Resolve HTTP Service Error..! Now it is resolved..
817.6. Bharat Kaushik (11/17/2012 05:05 PM)
Thanks for a very useful information.
his seems to be a common problem with all Anti Virus Programs. I had the same issue with Eset NOD32. I have searched a lot with different sites, now finally I got the answer & able to solve the problem.