Home/ Questions/Q 6906685
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T08:20:29+00:00

One of the services works fine but the other always throws a Socket Timeout

  • 0

One of the services works fine but the other always throws a Socket Timeout ‘forcibly closed’ error.

I have portSharingEnabled=’true’ on both services and the netTcp Port Sharing windows service switched on.

I’ve done a lot of research on this but am unable to find the cause, any suggestions?

It’s not an option to change the port either due to legacy system setup.

Each netTcp Binding looks liks this: 

8033:*

Is that right or is the * the issue here? I’ve run out of ideas as you can tell.

Last point: It definitely isn’t a timeout issue as I get the error on the client side instantly each time. All other binding config values are matched on both server/client side and set close to max as suggested by other similar issues here on SO.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Hard to tell for sure. To diagnose the issue further, for the service and the client I would enable WCF Tracing and see if there is an underlying exception. Here’s a good blog article on how to create and read the log using the tools included with Visual Studio:

    http://www.atulverma.com/2011/10/enable-wcf-tracinglogging-using.html

    • 0