Sql Server Event Id 9724

  • Hi All,

    Event Source:MSSQLSERVER

    Event Category:(2)

    Event ID:9724

    Description:

    The activated proc [LakeSideLockLogger].[_LakeSide_DbTools_LockMonitorEvents] running on queue msdb.LakeSideLockLogger._LakeSide_DbTools_LockQueue output the following: 'Difference of two datetime columns caused overflow at runtime.'

    Please help me out for this issue generating every 15 sec in eventviewer.

  • It looks like you may have a stored procedure that is attempting to convert dates and the result is an out of range condition. Have you checked the code in those procedures to see what it's doing?

  • Bjhogan is right. It think this has something to do with the datatype conversions like smalldatetime and datetime conversions and some times could be due to entering NULL values for the datetime columns. Try to check the code.

    Thank You,

    Best Regards,

    SQLBuddy

  • Thanks for your response.

    But it is a system stored procedure and it was encrypted. couldn't able to identify the code written.

  • Check out this post for decrypting stored procedures.

    http://www.sqlservercentral.com/scripts/SQLInsider+Scripts/30622/

  • the function below is for SQL 2000 only; if you run it on 2005/2008/R2, all it does is drop teh encrypted procedure, but does not recreate it.

    bjhogan (12/15/2010)


    Check out this post for decrypting stored procedures.

    http://www.sqlservercentral.com/scripts/SQLInsider+Scripts/30622/

    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!

  • Thanks for pointing this out Lowell. The server that I tried this on, just happened to be a 2000 server. Didn't really even pay attention to the version I was running on.

    So yeah...don't run this unless you want to drop your procedure.

  • i think the recommended way is to connect via a dedicated admin connection (DAC);

    I belive when you do that, all procs are decrypted automatically when you view them, to assist in debugging issues.

    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 8 posts - 1 through 7 (of 7 total)

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