<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Understanding the error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.”</title><link>http://blogs.msdn.com/sql_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx</link><description>This error message, which is associated with the Winsock error WSAENOBUFS and actually comes from Windows rather than SQL Server directly, has two well-understood root causes. However, it still stumps people today, probably because there is no single</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Blog: SQL Protocols | Bscopes Feeds</title><link>http://blogs.msdn.com/sql_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx#9472447</link><pubDate>Fri, 13 Mar 2009 03:55:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9472447</guid><dc:creator>Blog: SQL Protocols | Bscopes Feeds</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://feeds.bscopes.com/2009/03/12/blog-sql-protocols/"&gt;http://feeds.bscopes.com/2009/03/12/blog-sql-protocols/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Understanding the error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.”</title><link>http://blogs.msdn.com/sql_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx#9775370</link><pubDate>Thu, 18 Jun 2009 12:56:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9775370</guid><dc:creator>George Tsirogiannis</dc:creator><description>&lt;p&gt;This error also comes up as a consequence of poor handling of the asynchronous socket receiving operation, like:&lt;/p&gt;
&lt;p&gt;Sub ClientListening()&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;While True&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;ClientSocket.BeginReceive(SocketBuffer, 0, BufferSize, SocketFlags.None, AddressOf ReceiveCallback, Nothing)&lt;/p&gt;
&lt;p&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;End While&lt;/p&gt;
&lt;p&gt;End Sub&lt;/p&gt;
</description></item><item><title>re: Understanding the error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.”</title><link>http://blogs.msdn.com/sql_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx#9864755</link><pubDate>Tue, 11 Aug 2009 21:33:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9864755</guid><dc:creator>jacob</dc:creator><description>&lt;p&gt;I'm using Opera 9.64, and if I leave my browser on the below page, it will start prompting for a username and password after five or fifteen minutes. This is incredibly annoying.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/sql_protocols/archive/2005/10/22/sql-server-2005-connectivity-issue-troubleshoot-part-i.aspx"&gt;http://blogs.msdn.com/sql_protocols/archive/2005/10/22/sql-server-2005-connectivity-issue-troubleshoot-part-i.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Otherwise, great blog, the information here is much appreciated.&lt;/p&gt;
</description></item></channel></rss>