Comments on: On ADO.NET Connection Pooling and SQL Server Error 10054 http://nicholas.piasecki.name/blog/2009/05/on-ado-net-connection-pooling-error-1005/ Confessions of a small business software developer Sat, 04 Feb 2012 19:02:06 +0000 hourly 1 http://wordpress.org/?v=3.0.5 By: lior http://nicholas.piasecki.name/blog/2009/05/on-ado-net-connection-pooling-error-1005/comment-page-1/#comment-1874 lior Wed, 06 Apr 2011 19:16:18 +0000 http://nicholas.piasecki.name/blog/?p=240#comment-1874 need to be sqlException.Number and not ErrorCode need to be sqlException.Number and not ErrorCode

]]> By: dannygibor http://nicholas.piasecki.name/blog/2009/05/on-ado-net-connection-pooling-error-1005/comment-page-1/#comment-1344 dannygibor Tue, 18 Aug 2009 12:36:08 +0000 http://nicholas.piasecki.name/blog/?p=240#comment-1344 Thanks for the code. I suggest to move the retry = false into the try{} block. try { retry = false; reader = command.ExecuteReader(commandBehavior); } Otherwise you might call the ExecuteReader more than once Thanks for the code.
I suggest to move the retry = false into the try{} block.

try
{
retry = false;
reader = command.ExecuteReader(commandBehavior);
}

Otherwise you might call the ExecuteReader more than once

]]>