Symptoms
During "heavy load" periods most of the running processes fail with following error:
"Exception has been thrown by the target of an invocation. Insufficient winsock resources available to complete socket connection initiation. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full".
Diagnoses
Most likely these symptoms indicate that custom code (e.g. custom service broker) used in environment does not close opened connections properly causing errors mentioned above. In addition to this you may want to review the following Microsoft KB: "Kernel sockets leak on a multiprocessor computer that is running Windows Server 2008 R2 or Windows 7"
In some scenarios it may be necessary to adjust values in the following registry settings:
KEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesTcpipParametersMaxUserPort = 60000 HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesTcpipParametersTcpTimedWaitDelay = 30
See details on Stackoverflow - Insufficient winsock resources
Resolution
Most frequent cause of such issues is custom code used in environment - review it and make sure that all connections are properly closed, since this might also lead to such errors.
