Is this query being executed asynchronously against a connection that has been disposed (e.g. via exiting a 'using' block, etc)?

It may be useful to see the associated C# code that is triggering this issue.