50000 error executing stored process

  • Doubt it.

    Not handling the error in sQL does not mean you're ignoring it. It means SQL throws the error to the application. Hence you should see the error in the app. However that is not an error from SQL. I suggest you debug the app first.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Hi ,

    I have seen an article regarding transaction Isolation.. may be the same is happening in this case and I have also found that "SET TRANSACTION" would also set to one of the isolation levels.

    I am thinking to use the same and set the transaction to "Serializable" so that dirty read, non repeated read issues can be eliminated.

    COuld you help me how i can set a particuralar transaction isolation level to "Serializable".

  • Books Online: Transaction Isolation Level

    Be sure to read up on the downsides of it too.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I have modified my process in the application to recall for one time if it got failed for this specific error (50000) and now it is all set . Juntwanted to update you.

    Thank you all very much for your help and time in this case...

    Regards,

    Mohan

  • Hi Grasshopper,

    Did you get the answer for this question. Because I am facing the same problem .If got the answer, please let me know

    Thank you

    sandy

  • sandeep1553 (4/2/2015)


    Did you get the answer for this question. Because I am facing the same problem .If got the answer, please let me know

    Error 50000 is a user-defined error. It means that somewhere in the procedure there's a RAISERROR command which is raising a user-defined error. It's not something that there's a generic solution to, you need to look at your procedure and see why the RAISERROR command is run.

    It is not system-generated, it is not something that someone unfamiliar with your code can answer.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • sandeep1553 (4/2/2015)


    Hi Grasshopper,

    Did you get the answer for this question. Because I am facing the same problem .If got the answer, please let me know

    Thank you

    sandy

    look in your code for RAISERROR

    that is where the error is generated, and what you need to concentrate on, i think.

    RAISERROR('Obscure,poorly written message from developer',16,1)

    Msg 50000, Level 16, State 1, Line 1

    Obscure,poorly written message from developer

    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!

Viewing 7 posts - 16 through 21 (of 21 total)

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