net.tcp not working since upgrading to windows 10

Nick V picture Nick V · Aug 11, 2015 · Viewed 8.6k times · Source

After upgrading from windows 8.1 to windows 10, None of the projects that have a WCF service available through net.tcp connections are able to connect.

The exception i get is:

The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '19:59:59.9769910'

the inner exception code is: 10054

But the exception happens right away. So it's not a time-out.

I checked IIS and everything is still configured right. (still have the right binding on the site, enabled protocols http,net.tcp)

I checked my services if net.tcp listener adapter was running and it was.

I checked windows features and saw that windows communication foundation non-http activation was turned off. so i turned it on and restarted my PC and still get that same exception.

I've waisted a total of 4 hours so far trying to get the net.tcp connection to work but i'm kind of losing hope here.

here are the windows features i've turned on:

enter image description here

and here are the windows services i have running:

enter image description here

Did anyone else run into this issue when upgrading to windows 10?

Answer

Christian Myksvoll picture Christian Myksvoll · Nov 4, 2015

I finally got it working after hours of trial and error. I am not 100% sure if this is what actually solved my problem in the end, but give it a try:

  1. Open "Turn Windows features on or off"
  2. Uncheck "WCF Services" and all underlying boxes
  3. Reboot computer
  4. Recheck "TCP Activation", "TCP Port Sharing" under "WCF Services" (and any other activation methods you need)
  5. Reboot computer