What port is Profiler using for its remoting server?

bdang@meridianlink.combdang@meridianlink.com Posts: 2
edited April 7, 2005 12:38PM in ANTS Performance Profiler Previous Versions
I'm getting the following exception error in the Event Log when I try to start this service.

Service cannot be started. System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port)
is normally permitted
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider)
at System.Runtime.Remoting.Channels.Tcp.TcpChannel..ctor(IDictionary properties, IClientChannelSinkProvider clientSinkProvider, IServerChannelSinkProvider serverSinkProvider)
at Service.Service1.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
· Share on Twitter

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hello,

    The ANTS Profiler Service listens on TCP port 8087, so it will probably fail if you have another service listening on the same port. You can use the netstat -a command to find out which ports are in use. If you find that something is listening on 8087, you can stop that service and run the ANTS Profiler Service.

    This service is used to help profile ASP .NET applications, so if you're not planning on doing that, then you can disable the service and not need worry any more about it.
    · Share on Twitter
This discussion has been closed.