Post reply

Job was failed

  • November 14, 2011 at 7:18 am

    #246057

    Hi Team,

    Job was failed due to this error,

    Error 50001, severity 16, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. [SQLSTATE 42000] (Error 18054). The step failed.

    I had searched in msdn i got the below information

    http://ignaciosalom.com/2010/01/17/sql-2005-errors-18054-50001/

    Can you please suggest me, How can i work out here. i m bit confusing..

    Thanks in advance.

  • November 14, 2011 at 7:27 am

    #1407151

    2nd post today about this issue.

    I'm giving this thread as reference so you guys can help one another.

    http://www.sqlservercentral.com/Forums/Topic518471-146-1.aspx

  • November 14, 2011 at 8:47 am

    #1407235

    Hi Team,

    that is different one.

    Tx

  • November 14, 2011 at 8:50 am

    #1407239

    I've helped as much as I could. I don't know anything about that error.

  • November 15, 2011 at 12:50 am

    #1407647

    50001 is a user defined error, not a system error.

    You first need to find out which application\database has created this error and when it's fired.

    You can also check in sys.messages if there is a message text defined for this error or not.

    select * from sys.messages

    where message_id = 50001

    [font="Verdana"]Markus Bohse[/font]

  • November 15, 2011 at 2:57 am

    #1407688

    Hi team,

    I have checked this command

    select *from sys.messages

    where id = 500001

    but i m not getting any result, any suggestions on this.

  • November 15, 2011 at 3:06 am

    #1407690

    Add as much logging as possible in your job. And also set a ouput file for the job. This can be done in Advanced options of the job. From the Job history you cannot get the detailed information of the jab failure. But this type of output file will have the exact error where the job stopped.

    Hope this will help you.

  • November 15, 2011 at 3:20 am

    #1407699

    What exactly is your job doing?

    Does it run a TSQL script or a stored procedure which contains a RAISERROR (50001,16,1) ?

    In that case if error number 50001 is not defined in sys.messages you would receive that kind of error because no message is defined for this error.

    [font="Verdana"]Markus Bohse[/font]

  • November 15, 2011 at 3:33 am

    #1407703

    fdsfdsf

  • November 15, 2011 at 3:52 am

    #1407720

    I see 2 times your calling RAISERROR 50001

    RAISERROR (50001, -- Message id.

    16, -- Severity,

    1, -- State,

    N'xp_cmdshell call in [dbo].[adminManagePartition_Trace] failed. Purge not complete.'); -- First argument supplies the string.

    Since you already stated that there's no error message 50001 defined in sys.messages you receive the error. Change the code to this and it should work:

    RAISERROR (50001,

    N'xp_cmdshell call in [dbo].[adminManagePartition_Trace] failed. Purge not complete.',

    16,1)

    [font="Verdana"]Markus Bohse[/font]

Viewing 10 posts - 1 through 9 (of 9 total)

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