none
SQL 2008R2 SP2 spamming Application log on Active node RRS feed

  • Question

  • After installing SQL 2008R2 SP2 on our 2-node SQL failover cluster (Windows 2008R2 SP1) I started to see a lot of following informational events on the clusters active node logs:

    Log Name:      Application
    Source:        SQLSERVERAGENT
    Date:          24.08.2012 10:25:11
    Event ID:      53
    Task Category: Failover
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      node2
    Description:
    [sqagtres] CheckServiceAlive: returning TRUE (success)

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="SQLSERVERAGENT" />
        <EventID Qualifiers="16384">53</EventID>
        <Level>4</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-08-24T07:25:11.000000000Z" />
        <EventRecordID>167169</EventRecordID>
        <Channel>Application</Channel>
        <Computer>node2</Computer>
        <Security />
      </System>
      <EventData>
        <Data>[sqagtres] CheckServiceAlive: returning TRUE (success)
    </Data>
        <Binary>350000400400000004000000730071006C00000000000000</Binary>
      </EventData>
    </Event>

    This event pops in log every 5 seconds, that is the standard polling time for failover cluster.

    Is this by design that it should spam the log or something that I have overlooked on my configuration?

    Friday, August 24, 2012 7:22 AM

Answers

  • This issue has been fixed in Cumulative update package 3 for SQL Server 2008 R2 Service Pack 2 and Cumulative update 3 for SQL Server 2012

    http://support.microsoft.com/kb/2718920

    Wednesday, December 19, 2012 11:38 AM

All replies

  • Friday, August 24, 2012 5:32 PM
  • Found it too, was hoping that someone knows a solution already.
    Saturday, August 25, 2012 8:10 AM
  • Checked that Bug link today again, and it is "Closed as Duplicate". So in my mind it is not solved nor is someone looking into it. Because of that I'd like to keep this thread alive to get some sort of solution/workaround quickly.
    Monday, September 3, 2012 7:28 AM
  • Yes, Karol. Bug link says it is duplicate (with Closed status), however, there is no fix for SQL 2008 R2. I do see Cumulative update # 3 for SQL 2012 but no solution for SQL 2008 R2 (with Service Pack 2). I am seeing this issue in two nodes windows 2008 r2 (SP2) Cluster running SQL 2008 R2 (SP2).

    We need prompt respones from Microsoft Engineers to reslove this issues in our production server, it is making SPAM Logging in Application Log.

    Thanks

    AB

    Tuesday, September 4, 2012 2:03 AM
  • Still no response from Microsoft on this at all??? Unbelievable, meanwhile my logs fill up daily with no way to shut the feature off other than expanding the timing of the regular status checks (which defeats the purpose of having a failover cluster)... Unreal after this long.

    • Proposed as answer by Akbarov Nazim Wednesday, November 20, 2013 3:39 PM
    Tuesday, October 9, 2012 3:48 PM
  • Hello Jeff,

    We are working on addressing this issue in SQL 2008 R2 SP2.

    Please take a look at latest comments in http://connect.microsoft.com/SQLServer/feedback/details/737820/sql-2012-cluster-checkservicealive-spams-application-event-log

    Thanks

    Sethu Srinivasan [MSFT]

    SQL Server

    Sunday, October 14, 2012 3:08 AM
    Moderator
  • Sethu,

    I do not know why you send us sql 2008 users to a link that tells us nothing about what you are doing for 2008?

    The only interesting piece was this:

    "I meant to add that you need to stop and start the SQL Agent service for the change in polling intervals to take effect. "  But it does not say anything about what or where to change this polling interval?

    Can you please provide a workaround for this?  We are not going to 2012 anytime soon and I need to view the event logs without all of this stupid noise!

    Mo


    Mo G

    Wednesday, December 19, 2012 11:32 AM
  • This issue has been fixed in Cumulative update package 3 for SQL Server 2008 R2 Service Pack 2 and Cumulative update 3 for SQL Server 2012

    http://support.microsoft.com/kb/2718920

    Wednesday, December 19, 2012 11:38 AM
  • Has anyone had success with this cumulative patch - specifically to solve the Event ID spamming problem?
    Thursday, March 7, 2013 7:10 PM
  • Yes. please apply the fix after which you will not see these messages anymore
    http://support.microsoft.com/kb/2718920
    Thursday, March 7, 2013 7:57 PM
  • Has anyone had success with this cumulative patch - specifically to solve the Event ID spamming problem?

    It stopped spamming logs after installing CU3
    • Proposed as answer by Sam Kenny Monday, March 11, 2013 2:55 PM
    Monday, March 11, 2013 2:47 PM
  • Interestingly enough, I was hit by this over the weekend.   I had a two node SQL Cluster up and running with a default and named instance of SQL 2012 RTM, two named instances of SQL Server 2008 R2 SP2, and a named instance of SQL Server 2008 SP3.  I had read about this bug when building the cluster, and watched for the dreaded Event ID 53 errors, but I never saw a one.

    Over the weekend, we ran some Windows updates on the Cluster, actually, here's the list...  KB2799494, KB2789645, KB2251487, KB2790655, KB2538243, KB890830, KB2790113, KB2789642, KB2797052, KB2687441, KB2596672, KB2778344, KB2645410, KB2792100, KB2538242

    After updating then rebooting the passive node, then failing over all SQL instances to it, it started to be spammed with Event ID 53!    And it was reporting it for ALL 5 instances, including the SQL 2008 instance!

    I installed the SQL Server 2008 R2 SP2 CU3 hot fix for both nodes, and that stopped the flooding for the two named 2008 R2 SP2 instances.  After installing SP1 for SQL 2012, that stopped both of those instances and the SQL 2008 instance.


    Jason Fay Sr SQL Server DBA Joy Global Inc

    Monday, March 11, 2013 6:41 PM