Question : Periodic error in SSMS SQL Server 2008 R2

I have already submitted this to Microsoft, and gotten no answer, so perhaps someone can shed some light on the situation.

I recently upgraded my SQL Server 2008 to 2008 R2, and ever since then, I get periodic errors as shown in the screenshots attached.

This is NOT from a web page or another application. This happens in SQL Server Management Studio when I click on a table to expand it to see Columns, Keys, Constraints, etc.

I do have MS Access 2010 that uses linked tables running in a vmware virtual machine that connects to this database, but there is nothing (obvious) that would cause this condition. The table I clicked on doesn't even have code (yet) to access this table. It is not one particular table that causes problems either. It is just that the most recent error happened to be on a table that is not being accessed. In the past, it has happened on other tables, but I don't remember if the virtual machine was even loaded at the time (which would mean that the tables were not being accessed by any application).

Anyway, I am looking for some ideas, as I get this error infrequently, but it only started happening when I went to Sql Server 2008 R2 (from SQL Server 2008).

Attachments:

DataReaderError.PNG (31 KB) (File Type Details) 

DataReader Error

SQLIsBusy.png (7 KB) (File Type Details) 

The dreaded IS BUSY message

Answer : Periodic error in SSMS SQL Server 2008 R2

Hi,

This is due to a change in the default setting for MARs.  It used to be  on by default and we changed it to off by default post RC1.  So just  change your connection string to add it back (add  MultipleActiveResultSets=True to connection string).

For more info:

http://www.netknowledgenow.com/blogs/onmaterialize/archive/2006/09/20/fixing-the-_2200_there-is-already-an-open-datareader-associated-with-this-command-which-must-be-closed-first_2e002200_-exception-in-entity-framework.aspx


Change it in the connection string, restart the applications and then check again through SSMS... this should be solving the issue.

Bye.