I have a problem with openaccess's profiler.
Windows 8 pro, visual studio 2012, firewall down.
In a console application
static void Main(string[] args)
{
string line;
Telerik.OpenAccess.ServiceHost.ServiceHostManager.StartProfilerService(12222);
do
{
line = Console.ReadLine();
new Program().SelectMetod(line);
} while (line != null);
}
the application works correctly, but when i try to connect with profiler and test connection appears:
"No connection could be made because the target machine actively refused it 127.0.0.1:12222"
the same with 15555 or other port.
Can you help me?
8 Answers, 1 is accepted
Unfortunately we were not able to reproduce the issue in our test environment. It seems that this is not a problem in Telerik OpenAccess Profiler.
I would suggest you to use an external tool to see the state of the port after you start the profiler service. You could use the Microsoft Windows CommandLine and the "netstat" command which will give you the state of all open ports. The 12222/15555 port should be in a "Listening" state.
I suppose that there is an another program different than a firewall which stops the access to the port.
Do not hesitate to get back to us in case the port seems to be open but the issue remains.
Regards,
Boris Georgiev
Telerik
Rank 1
C:\Windows\system32>netstat -aon
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 868
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:808 0.0.0.0:0 LISTENING 5876
TCP 0.0.0.0:2179 0.0.0.0:0 LISTENING 2180
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 580
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 932
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 964
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 696
TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING 2568
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING 704
TCP 0.0.0.0:51103 0.0.0.0:0 LISTENING 9856
TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING 2080
TCP 127.0.0.1:13377 0.0.0.0:0 LISTENING 1648
TCP 127.0.0.1:51104 0.0.0.0:0 LISTENING 9856
TCP 169.254.80.80:139 0.0.0.0:0 LISTENING 4
TCP 192.168.137.97:139 0.0.0.0:0 LISTENING 4
TCP 192.168.137.97:57509 157.56.124.77:443 ESTABLISHED 4716
TCP 192.168.137.97:57588 66.196.66.212:443 ESTABLISHED 5216
TCP 192.168.137.97:57589 66.196.66.212:443 ESTABLISHED 5216
TCP [::]:135 [::]:0 LISTENING 868
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:808 [::]:0 LISTENING 5876
TCP [::]:2179 [::]:0 LISTENING 2180
TCP [::]:5357 [::]:0 LISTENING 4
TCP [::]:49152 [::]:0 LISTENING 580
TCP [::]:49153 [::]:0 LISTENING 932
TCP [::]:49154 [::]:0 LISTENING 964
TCP [::]:49156 [::]:0 LISTENING 696
TCP [::]:49157 [::]:0 LISTENING 2568
TCP [::]:49158 [::]:0 LISTENING 704
TCP [::]:51103 [::]:0 LISTENING 9856
TCP [::1]:808 [::1]:51536 ESTABLISHED 5876
TCP [::1]:49155 [::]:0 LISTENING 1984
TCP [::1]:51104 [::]:0 LISTENING 9856
TCP [::1]:51536 [::1]:808 ESTABLISHED 900
UDP 0.0.0.0:68 *:* 932
UDP 0.0.0.0:500 *:* 964
UDP 0.0.0.0:3702 *:* 992
UDP 0.0.0.0:3702 *:* 992
UDP 0.0.0.0:3702 *:* 2604
UDP 0.0.0.0:3702 *:* 1820
UDP 0.0.0.0:3702 *:* 2604
UDP 0.0.0.0:3702 *:* 1820
UDP 0.0.0.0:4500 *:* 964
UDP 0.0.0.0:5355 *:* 1160
UDP 0.0.0.0:53672 *:* 2604
UDP 0.0.0.0:56482 *:* 992
UDP 0.0.0.0:61075 *:* 1820
UDP 127.0.0.1:1900 *:* 2604
UDP 127.0.0.1:49965 *:* 6904
UDP 127.0.0.1:54696 *:* 10768
UDP 127.0.0.1:56481 *:* 2604
UDP 127.0.0.1:56956 *:* 5260
UDP 127.0.0.1:57177 *:* 9120
UDP 127.0.0.1:59564 *:* 4356
UDP 127.0.0.1:60020 *:* 3732
UDP 127.0.0.1:61990 *:* 10208
UDP 127.0.0.1:62316 *:* 5216
UDP 127.0.0.1:62554 *:* 1572
UDP 127.0.0.1:64539 *:* 3816
UDP 169.254.80.80:137 *:* 4
UDP 169.254.80.80:138 *:* 4
UDP 169.254.80.80:1900 *:* 2604
UDP 169.254.80.80:56479 *:* 2604
UDP 192.168.137.97:137 *:* 4
UDP 192.168.137.97:138 *:* 4
UDP 192.168.137.97:1900 *:* 2604
UDP 192.168.137.97:56480 *:* 2604
UDP [::]:500 *:* 964
UDP [::]:3702 *:* 2604
UDP [::]:3702 *:* 992
UDP [::]:3702 *:* 1820
UDP [::]:3702 *:* 1820
UDP [::]:3702 *:* 2604
UDP [::]:3702 *:* 992
UDP [::]:4500 *:* 964
UDP [::]:5355 *:* 1160
UDP [::]:53673 *:* 2604
UDP [::]:56483 *:* 992
UDP [::]:61076 *:* 1820
UDP [::1]:1900 *:* 2604
UDP [::1]:56478 *:* 2604
UDP [fe80::1549:5c40:a7be:12ca%22]:1900 *:*
2604
UDP [fe80::1549:5c40:a7be:12ca%22]:56477 *:*
2604
UDP [fe80::4899:cfdb:5e00:2c7f%30]:546 *:*
932
UDP [fe80::4899:cfdb:5e00:2c7f%30]:546 *:*
932
UDP [fe80::4899:cfdb:5e00:2c7f%30]:1900 *:*
2604
UDP [fe80::4899:cfdb:5e00:2c7f%30]:56476 *:*
2604
The profiler and the application is open, but i can't find the 15555 port
At this point we lack information on the reasons why the port 15555 is not visible - we believe this problems could be resolved only locally, based on the specifics of the infrastructure. Unfortunately, ensuring an open port is a requirement for the OpenAccess Profiler to work properly.
Do not hesitate to get back to us in case you manage to apply a local change in order to make the port visible and we can assist you further with setting up the Profiler connection.
Regards,
Kristian Nikolov
Telerik
Rank 1
System.Net.Sockets.SocketException occurred
HResult=-2147467259
Message=Only one usage of each socket address (protocol/network address/port) is normally permitted
Source=System
ErrorCode=10048
NativeErrorCode=10048
StackTrace:
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
The debugger shows it's trying to open a listening socket on port on 808, which is already in use by net.tcp. Dario's netstat output shows port 808 in use as well. When I move net.tcp out of the way it works correctly, but it's rather inconvenient for us to have to move net.tcp to a different port to be able to do profiling.
Thank you for the provided information. We will need a bit more time to investigate this and we will let you know as soon as we have more information on the matter. In the meantime can you please provide us the call-stack of the thrown exception. It will greatly help for our investigation.
Regards,
Boris Georgiev
Telerik
Rank 1
System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:808. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.ServiceModel.Channels.SocketConnectionListener.Listen()
--- End of inner exception stack trace ---
at System.ServiceModel.Channels.SocketConnectionListener.Listen()
at System.ServiceModel.Channels.ConnectionAcceptor.StartAccepting()
at System.ServiceModel.Channels.ExclusiveTcpTransportManager.OnOpen()
at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at Telerik.OpenAccess.ServiceHost.ServiceHostManager.StartProfilerService(Int32 port)
I looks like the profiler tries to create it's own net.tcp server on the default port...
Thank you for the provided information. We are able to investigate the issue in more details now. We will notify you in this thread when we have any information.
Please excuse us for the inconvenience caused and feel free to contact us if you need any assistance working with Telerik Data Access.
Regards,
Boris Georgiev
Telerik
Unfortunately with all provided information we were not able to reproduce the issue. In our test environment we have tried different setups - enabling and disabling port 808, starting Net.TCP Port Sharing Service and using different applications to listen on this port, but we did not encounter any problems with Telerik Data Access Profiler and profiling application.
If you still encounter this issue and you have more information how to reproduce it, please let us know.
Regards,
Boris Georgiev
Telerik