Post reply

A severe error occurred on the current command. The results, if any, should be discarded

  • March 31, 2017 at 5:31 am

    #320056

    Dear All

    Currently i am working in sql server 2005, While executing staored procedure with parameter i am facing followiing problem

    A severe error occurred on the current command. The results, if any, should be discarded

    Msg 0, Level 11, State 0, Line 0
    A severe error occurred on the current command. The results, if any, should be discarded.

    Please suggest me a good solution.

  • March 31, 2017 at 5:36 am

    #1935944

    That Msg 0/State 0/Line 0 is upsetting; i expect better error reporting than that.

    it might be a known issue, that requires updating to the latest patches for 2005; the link below explains it.
    look in the SQL error log, and see if at the same time, you saw any additional error messages; the article below implies the consumption of a view and a specific error in the error log

    Date Time Server Error: 17310, Severity: 20, State: 1.

    https://support.microsoft.com/en-us/help/938102/fix-error-messages-when-you-run-a-query-that-references-a-view-in-sql-server-2005-service-pack-2-a-severe-error-occurred-on-the-current-command.-the-results,-if-any,-should-be-discarded

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • April 3, 2017 at 6:51 am

    #1936254

    Does the SP, or triggers on any of the tables it updates, use the NOLOCK hint or run in READ UNCOMMITED isolation?

    If so, get rid of the hint as it will be prone to errors when data movement is occuring.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply