Tag Info

New answers tagged

1

An alternative, is if you are processing a higher volume of records, you may actually be getting a misleading error. It could be that you have used up all of your ports on your PC, you can check this by running Sysinternals TCPView. If you see thousands of TIME_WAIT, this is a possible cause. In essence, after your application closes its connection to the ...


3

It looks like you have an application that isn't properly closing or disposing of the SqlConnection objects. By default, SqlConnection has a max pool size of 100. The fix here would be to work with the application to find out why connections aren't being cleaned up, as they are still "active" in the particular connection pool, which is why you are unable ...



Top 50 recent answers are included