“An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full”

Question

I\'ve written an IP multicasting application in C#. It compiles fine, but at runtime this line:

sock.SetSocketOption(SocketOptionLevel.IP,
                          


        

Answer 1

I have this same error, but only on Windows 7. If I run my same multicast app on Vista it works. It pops up a system dialog to unblock the behavior from the app, but it runs. This is probably a changed networking permissions thing in win7. I'm still looking for a solution. If someone else finds one, please post.

Answer 2

Got this error when contacting an external email provider in Sweden called Loopia on a Windows Server 2012 R2 Datacenter x64.

The server had not been rebooted for almost a year. After rebooting everything worked.

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 194.9.94.72:993

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 194.9.94.72:993

Answer 3

see - http://support.microsoft.com/kb/2553549 and https://support.microsoft.com/en-us/kb/929851 (you determine how many dynamic outbout ports you want). Along with this second article, set the TcpTimedWaitDelay to dword decimal value of 30. So when sockets get released to the system, the clear faster. See - technet.microsoft.com/en-us/library/cc938217.aspx

Answer 4

It could be port exhaustion. When application(s) makes too many outgoing connections in short time frame or does not dispose outgoing connections properly - you run out of ports.

Here is the link to rather lengthy explanation and a way to diagnose the issue

Answer 5

I had the same error on Windows Server 2008. In my case, after restart the server (with 2 years uptime) problem solved.

Answer 6

I've had the same issue (a.k.a error 10055) when trying to connect to a local MySQL database. I believe you need to raise the number of dynamic ports that the operating system allows.

The solution that worked for me was mentioned here I believe it may help you as well, since you are using Windows. Best of luck!