SharePoint on Junian Dev

Solving Sharepoint ClientContext Socket Exception in C#

author@junian.dev (Junian Triajianto) — Fri, 07 Sep 2018 06:39:53 +0700

So, you’ve been writing a Sharepoint client application and it’s running just fine. After several weeks or months, you noticed some errors were showing up. If you see a lot of SocketException error messages like following snippet, then this article is for you.

System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted 127.0.0.1:443
     at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
     at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

In my previous article about Sharepoint CSOM Socket Exception, I wrote about on how to solve this issue by editing some registry values. I did it and worked beautifully, but only for several days.

Sharepoint CSOM Socket Exception

author@junian.dev (Junian Triajianto) — Mon, 06 Aug 2018 13:45:14 +0700

UPDATE (2018-09-05): New additional solution by changing TCP TIME_WAIT delay.

Months ago I’ve made a C# script to synchronize data from external source into a Sharepoint Site using Sharepoint CSOM and PnP. It’s been running just fine until recently it stopped working. I saw the logs and see a lot of SocketException error messages like the one below.

System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted 127.0.0.1:443
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

So then I did a research and found a stackoverflow.com thread which have a simple explanation by jrista on why it happened.