azuredatastudio: Query failed: The connection does not support MultipleActiveResultSets.

I’m not sure if this is a bug related to Azure data studio or if there is something else that’s causing this but I’m getting the error “Query failed: The connection does not support MultipleActiveResultSets.” when I’m trying to execute a simple SQL.

query error

The SQL that I’m executing is: SELECT TOP (1000) [Id] ,[UserId] ,[CreatedOn] ,[CountryId] FROM [dbo].[TargetLocation]

Steps to Reproduce:

  1. This happened today, and I was unable to reproduce or get a step by step on how to reproduce this.

I solved this closing and reopening Azure data studio.

Version info: Version 1.2.4 Commit 1ebfd0235690ad044ed2874a02e65188f5fea01c Date 2018-11-02T21:50:52.634Z VS Code 1.26.1 Shell 2.0.9 Renderer 61.0.3163.100 Node 8.9.3 V8: 6.1.534.41 Architecture x64

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 13
  • Comments: 20 (2 by maintainers)

Most upvoted comments

Seconded. We first get an error re: ‘connection closed’ and then get this error on re-attempting to run the query. We can never come back to queries after more than 10 minutes or so, we have to close the tab and start a new one in order to establish a connection again.

Same here as everyone else. Nowadays I don’t wait for the error anymore, if I leave a tab unattended for more than 5 minutes then I proactively close it and right click database > new query again. This seems like a basic functionality that should be sorted out IMO.

Is there any chance you had the query window open and connected for a long time before running the query that returned this error, or that there was something else that might have caused your query to get disconnected for some reason?

I’ve seen this error message once or twice lately and I think it has something to do with our recent changes to make query tabs more resilient to getting unexpectedly disconnected, but am not entirely sure how to reproduce it