Sql Server Event Id 9724

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » Sql Server Event Id 9724

Sql Server Event Id 9724

Rate Topic

Display Mode

Topic Options

Author

Message

yvarjun

Posted Wednesday, December 08, 2010 11:41 PM

SSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 1:29 AM
Points: 36, Visits: 213

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

bjhogan

Posted Tuesday, December 14, 2010 6:55 AM

Valued Member

Group: General Forum Members
Last Login: Wednesday, March 20, 2013 8:42 AM
Points: 56, Visits: 376

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

sqlbuddy123

Posted Tuesday, December 14, 2010 10:59 AM

Right there with Babe

Group: General Forum Members
Last Login: Tuesday, May 21, 2013 3:17 PM
Points: 715, Visits: 1,524

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

yvarjun

Posted Wednesday, December 15, 2010 1:14 AM

SSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 1:29 AM
Points: 36, Visits: 213

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

bjhogan

Posted Wednesday, December 15, 2010 5:49 AM

Valued Member

Group: General Forum Members
Last Login: Wednesday, March 20, 2013 8:42 AM
Points: 56, Visits: 376

Check out this post for decrypting stored procedures.

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

Post #1035058

Lowell

Posted Wednesday, December 15, 2010 6:24 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 5:28 AM
Points: 11,789, Visits: 28,065

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

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son

Post #1035073

bjhogan

Posted Wednesday, December 15, 2010 7:00 AM

Valued Member

Group: General Forum Members
Last Login: Wednesday, March 20, 2013 8:42 AM
Points: 56, Visits: 376

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

Lowell

Posted Wednesday, December 15, 2010 7:13 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 5:28 AM
Points: 11,789, Visits: 28,065

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

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son

Post #1035120

« Prev Topic | Next Topic »

Permissions