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

**Frank Jones** · Nov 15 '05, 12:39 PM

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

Could this be it? I have 3 adaptors in my system - which doesn't seem to
add up to 50. But it sounds like the same issue. We're running Net 1.1.

Error - Office.com

http://support.microsoft.com/default.aspx?scid=kb;en-us;826757

"Frank Jones" <jones@jonsey.c om> wrote in message
news:eBaGpdRjDH A.4048@TK2MSFTN GP11.phx.gbl...[color=blue]
>
> When I call Dns.GetHostByNa me(Dns.GetHostN ame()) on one of our lab boxes I
> get the below exception. I've seen posts saying others in these[/color]
newsgroups[color=blue]
> have seen similar issues since moving to .Net. I currently can only
> reproduce it on one lab box. The box is running Windows 2000 Pro SP4. I
> can write C socket code that works fine - but .Net returns the below. Can
> anyone help?
>
>
> System.Net.Sock ets.SocketExcep tion : An operation on a socket could not be
> performed because the system lacked sufficient buffer space or because a
> queue was full
> at System.Net.Sock ets.Socket.Init ializeSockets()
> at System.Net.IPAd dress..cctor()
> at System.Net.Sock ets.Socket.Init ializeSockets() #0@0
> at System.Net.IPAd dress..cctor()# 0@0
>
>[/color]

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

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

Comment