Here’s an error I recently ran into when multiple threads started hitting my database:
There is already an open DataReader associated with this Command which must be closed first.
I’m using enterprise libraries Data Access Block and my DB is an SQL Server 2005. For once the fix was really easy, I just had to change my connection string to include MultipleActiveResultSets=True.
A nice easy immediate fix for a problem I thought would require some re-engineering. Why can’t all problems be like that