• Sign In
 
  • MSDN Blogs
  • Microsoft Blog Images
  • More ...
Common Tasks
  • Blog Home
  • Email Blog Author
  • RSS for comments
  • RSS for posts
Search
  • Advanced search options...
Tags
  • .NET Framewor
  • .NET Framework
  • Ajax/Javascript
  • ASP.NET
  • CLR
  • Cool stuff
  • DataAccess
  • Debugging/Windbg
  • Hotfix/Service Pack
  • IDEVDataCollector
  • IIS
  • Internet Explorer
  • Italian techs
  • LogParser
  • OT
  • Personal
  • Productivity
  • Random
  • Scripting/ASP
  • Security
  • Technology
  • Tools
  • Troubleshooting
  • Vista/Longhorn
  • Visual Studio
Archives
Archives
  • November 2010 (1)
  • October 2010 (1)
  • July 2010 (2)
  • April 2010 (1)
  • March 2010 (2)
  • February 2010 (2)
  • January 2010 (1)
  • October 2009 (2)
  • September 2009 (2)
  • August 2009 (1)
  • July 2009 (5)
  • June 2009 (1)
  • May 2009 (1)
  • April 2009 (3)
  • March 2009 (3)
  • February 2009 (5)
  • January 2009 (3)
  • December 2008 (5)
  • November 2008 (3)
  • October 2008 (2)
  • September 2008 (3)
  • August 2008 (3)
  • July 2008 (3)
  • June 2008 (5)
  • May 2008 (4)
  • April 2008 (8)
  • March 2008 (4)
  • February 2008 (5)
  • January 2008 (2)
  • December 2007 (4)
  • November 2007 (6)
  • October 2007 (6)
  • September 2007 (8)
  • August 2007 (6)
  • July 2007 (7)
  • June 2007 (10)
  • May 2007 (9)
  • April 2007 (12)
  • March 2007 (8)
  • February 2007 (5)
  • January 2007 (3)
  • December 2006 (1)
  • November 2006 (4)
  • October 2006 (2)
  • September 2006 (9)
  • August 2006 (2)
  • July 2006 (1)

Visual Studio debugger conflicts on port 80

MSDN Blogs > Never doubt thy debugger > Visual Studio debugger conflicts on port 80

Visual Studio debugger conflicts on port 80

Carlo Cardella
22 Jul 2007 10:37 AM
  • Comments 6

I personally got this problem on my laptop a while ago where IIS and Skype where involved, and even if this time the customer reported two different applications involved (Visual Studio 2005 and Cisco IP Communicator), the symptoms where the same: with Visual Studio 2005 and Cisco IP Communicator running ad the same time, he was unable to debug his web application with the message "Unable to start debugging on the web server.  Could not start ASP.NET or ATL Server debugging.  Verify that ASP.NET or ATL Server is correctly installed on the server". If he stopped the IP Communicator the problem went away; clearly a conflict between IIS and Cisco Communicator.

Just to be sure we had a look at "netstat -a -b", and found (as expected) that both applications were listening on the HTTP port

TCP    computername:http     computername.domain.com:0  LISTENING       492 [inetinfo.exe]

TCP    computername:http     computername.domain.com:0  LISTENING       3872 [Communicator.exe]

Since I don't know how Cisco IP Communicator works (and we can't support third party apps anyway), we decided to change the IIS port to 81, but this time the customer was getting "Unable to start debugging on the web server. Unable to connect to the web server. Verify that the web server is running and that incoming HTTP requests are not blocked by a firewall". Another tweak on customers firewall and the problem was fully resolved.

 

Carlo


Quote of the Day:
He is poor who does not feel content.
--Japanese proverb
  • 6 Comments
ASP.NET, IIS, Debugging/Windbg, Visual Studio
Leave a Comment
  • Please add 4 and 3 and type the answer here:
  • Post
Comments
  • dekos
    4 Oct 2007 9:13 AM

    Open the Windows regedit utility from the Command-line Interface (CLI) or through Start > Run.

    In the regedit utility, choose HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Communicator.

    From the Edit menu, choose New > DWORD value.

    Rename the WebServerDisabled value, and set it to any non-zero value.

    Note: This value does not appear by default.

    In order to enable the web server again, delete this key or set the key to zero.

  • Carlo Cardella
    4 Oct 2007 9:35 AM

    Ah... thanks for sharing!

  • OberData
    7 Feb 2008 8:00 PM

    Con motivo que me compre una nueva notebook es que tuve que reinstalar muchas aplicaciones y mudar mis...

  • duluca
    15 Feb 2011 6:53 AM

    This doesn't work with version 7

  • Sergi
    15 Jun 2011 8:49 AM

    In Windows 7 x64 with IIS7 creating this registry key doesn't work.

    I have Cisco IP Communicator 7.0.6.0 and in the install directory of this application: C:\Program Files (x86)\Cisco Systems\Cisco IP Communicator\ there is a file named: HTTPService.dll.

    Rename this file and close and open cisco ip communicator again.

    Next time you execute your CISCO IP telephone this service will not start.

  • Josep
    15 Jun 2011 8:55 AM

    Steps to disable the internal web server on Cisco IP Communicator version 7.0.6.

    1.- Switch off Cisco IP Communicator.

    2.- Open C:\Program Files (x86)\Cisco Systems\Cisco IP Communicator folder.

    3.- Rename HTTPService.dll to _HTTPService.dll or whatever...

    4.- Switch on Cisco IP Communicator

    Check http://localhost/ the internal web server is not there anymore.

Page 1 of 1 (6 items)
  • © 2012 Microsoft Corporation.
  • Terms of Use
  • Trademarks
  • Privacy Statement
  • Report Abuse
  • 5.6.402.223