Post reply

Error Notification from SQL Agent??

  • June 3, 2004 at 7:42 pm

    #163677

    We had with one of our servers yesterday which caused a whole pile of timeout errors. The culprit turned out to be Veritas BackupExec backing up the databases when it shouldn't have been (just another reason why I hate backup agents).

    I didn't get any notification from the server about any errors, just irate users ringing to find out what the problem was. The phone calls started at about 17:10.

    On subsequent examination I found no messages in the SQL Server Error Log and no messages in the Windows Event Log. What I did find was the following errors in the SQL Agent Log,

    2004-06-03 17:03:03 [298] SQLServer Error: 11, General network error. Check your network documentation. [SQLSTATE 08001]

    2004-06-03 17:03:08 [298] SQLServer Error: 258, ConnectionOpen (PreLoginHandshake()). [SQLSTATE 01000]

    2004-06-03 17:03:08 [382] Logon to server '(local)' failed (JobManager)

    These messages are then repeated almost every minute up until I killed the BackupExec process.

    My question is, how could I have gotten notification of the errors in the SQL Agent Log?

    --------------------
    Colt 45 - the original point and click interface

  • June 7, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • June 14, 2004 at 11:52 am

    #510325

    We have ran into the same problem on 2 different servers in the last week.  As for alerting to a problem, a script that checks the last date ran and compare against expected date to run would work ... Trigger a SMTP message if the results are not what is expected.

  • June 15, 2004 at 1:15 pm

    #510536

    You could write a stored proc to read the agent log into a table, and check the time stamp. If a new error is found, send e-mail, page, alert of your choice. 

    Steve

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

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