I was recently getting following error in my StreamInsight Application.
Could not connect to TCP error code 10061: No connection could be made because the target machine actively refused it.
The solution was very simple, I had to enable exception of the my port in my windows firewall. The way I figured it out was by quickly disabling the firewall (it was not a production server). Once I disabled it, the application just worked fine; this was a sign that the firewall was the cause of the issue, I right away enabled firewall and added my port as exception.
So many errors have cropped up recently due to the connectivity issue. I have started to make my routine to check firewall first before I move to next action item in my troubleshooting list.
When I sent this detail to my internal technical list of the expert, I got the suggestion that this error happens due to many other reasons as well and not only due to firewall.
I am interested to know when and how this error happens and what is the resolution. This way, if we have complete list, we can avoid this error in future.
Reference: Pinal Dave (http://blog.SQLAuthority.com)
Hello!
This execption/error stumps most developers/IT staff who have just recently been exposed to Windows Server 2008 R2. I belive the R2 blocks incoming transactions by default, while the vanilla-2008 did not. Therefore, all of a sudden a system/database that worked fine on a Windows 2008 Server fails to accept connections from remote machines when upgraded to run on Windows 2008 R2 Server.