I have not seen this before and am not quite sure where to start as I cannot reproduce it, it is happening on average once a day. Any ideas what this is typically or where to start looking?






Keith Chisarik

Everything I have googled about this says that it is a problem with commands that can take a significant amount of time to execute, so people will set the CommandTimeout property to a larger number and the process completes successfully.  However, if you're just opening the connection, then something else might be wrong.  Does this error come back immediately, or does your computer wait for 15 or 30 seconds before throwing the error?