2

I encountered this error message when trying to run a SEDE query (screenshot):

Line 0: A severe error occurred on the current command. The results, if any, should be discarded. Operation cancelled by user.

It's rather self-contradictory ("severe error occurred on the current command" vs. "Operation cancelled by user.") and I never canceled the operation anyway, so there is an error in the error message.

Improve this question
2
  • 10
    There is no SEDE magic happening between whatever SQL Server returns in case of an SQL Server query engine error and what gets shown in the UI. So what SQL Server dreams up is what you get. For reasons unknown to mankind SQL Server got in a state it is wildly guessing, including Operation cancelled by user. If you want a better error message, you have to contact Microsoft. Or find the reason why that query makes SQL Server angry. Maybe a disk is full / out of memory / network hick-up that made it bark like that. Commented Sep 21 at 19:13
  • 2
    There are some similar error messages in .NET that are confusing without enough context. The reason that a cancellation token triggers an abort can be an actual user aborting something, but often it is something else like a timeout. "Cancellation" usually means the code that called this decided to abort, not the code executing and throwing that exception. Commented Sep 22 at 8:38

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.