Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Sql Server Event Id 9724 Expand / Collapse
Author
Message
Posted Wednesday, December 8, 2010 11:41 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, October 15, 2015 1:20 AM
Points: 41, Visits: 237
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.
Post #1032308
Posted Tuesday, December 14, 2010 6:55 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 11:55 AM
Points: 56, Visits: 382
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?
Post #1034352
Posted Tuesday, December 14, 2010 10:59 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, January 23, 2015 2:58 PM
Points: 1,194, Visits: 2,243
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
Post #1034593
Posted Wednesday, December 15, 2010 1:14 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, October 15, 2015 1:20 AM
Points: 41, Visits: 237
Thanks for your response.
But it is a system stored procedure and it was encrypted. couldn't able to identify the code written.
Post #1034937
Posted Wednesday, December 15, 2010 5:49 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 11:55 AM
Points: 56, Visits: 382
Check out this post for decrypting stored procedures.

http://www.sqlservercentral.com/scripts/SQLInsider+Scripts/30622/
Post #1035058
Posted Wednesday, December 15, 2010 6:24 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 14,207, Visits: 37,133
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!
Post #1035073
Posted Wednesday, December 15, 2010 7:00 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 11:55 AM
Points: 56, Visits: 382
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.
Post #1035104
Posted Wednesday, December 15, 2010 7:13 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 14,207, Visits: 37,133
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!
Post #1035120
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse