May 16, 2008 at 7:22 am
I was running a query, getting results, then cancelled the query part way through. The cancel threw the following Exception, only I've never seen this error before and Google has nothing on it. Has anyone ever seen this message before?
If so, do you know what it means?
An error occurred while executing batch. Error message is: Exception of type 'Microsoft.SqlServer.Management.UI.Grid.StorageDataReader+StorageAbortedException' was thrown.
May 16, 2008 at 8:30 am
Nope. Never seen that one. Did it have any lasting effects, or did it just go away on its own?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
May 16, 2008 at 11:22 am
I was able to re-run my query without any problems. In fact, I haven't even closed out that session of SSMS yet. And haven't seen any additional error messages or anything odd since then.
Hopefully it's not important. @=) Though, from the look of the exception, I'd say it has something to do with the Results to Grid functionality (which is what I'm currently using in SSMS).
May 16, 2008 at 11:31 am
My guess (and guessing it is) is that you stopping it caused some problem with the grid creation. Maybe it was partway through creating the grid and had to interrupt a thread or something. Gross conjecture from the error message, but it's the best guess I can come up with. 🙂
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
May 16, 2008 at 11:35 am
And if there wasn't already a result set partially loaded, I'd agree with that.
You know how when you do a SELECT the results start loading as soon as the query is parsed and into processing? It was at that point when I stopped it. And I've stopped my queries in SSMS before at that point without this message.
Of course, if I didn't keep forgetting ORDER BY statements or WHERE clauses I wouldn't have to stop my query in the middle of running just so I could correct it. @=)
May 16, 2008 at 1:46 pm
Yeah, I've stopped plenty of queries at that point without that error. Weird.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply