• 25Mar

    We got this SCOM error last week along with a ton of the following warnings. Microsoft claims that this is a known issue that was supposed to be fixed with SCOM 2007 SP1 / SCOM 2007 R2, but I still encountered it running R2.

    Event Type: Error
    Event Source: DataAccessLayer
    Event Category: None
    Event ID: 26308
    Date:  3/11/2010
    Time:  11:30:01 AM
    User:  N/A
    Computer:
    Description:
    Query notification processing failed due to a sql exception.

    System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 – The semaphore timeout period has expired.)
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlCommand.CheckThrowSNIException()
    at System.Data.SqlClient.SqlCommand.InternalEndExecuteReader(IAsyncResult asyncResult, String endMethod)
    at System.Data.SqlClient.SqlCommand.EndExecuteReader(IAsyncResult asyncResult)
    at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryNotificationManager.HandleNotifications(Object state)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Error
    Event Source: Health Service Modules
    Event Category: Data Warehouse
    Event ID: 31569
    Date:  3/11/2010
    Time:  11:30:03 AM
    User:  N/A
    Computer:
    Description:
    Report deployment process failed to request management pack list from Data Warehouse. The operation will be retried.Exception ‘InvalidConnectionException’: ExecuteScalar requires an open and available Connection. The connection’s current state is closed.

    One or more workflows were affected by this.

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
    Instance name:
    Instance ID: {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
    Management group:

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: HealthService
    Event Category: None
    Event ID: 2115
    Date:  3/11/2010
    Time:  11:30:39 AM
    User:  N/A
    Computer:
    Description:
    A Bind Data Source in Management Group has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
    Workflow Id : Microsoft.SystemCenter.CollectDiscoveryData
    Instance    :
    Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: HealthService
    Event Category: None
    Event ID: 2115
    Date:  3/11/2010
    Time:  11:30:39 AM
    User:  N/A
    Computer:
    Description:
    A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
    Workflow Id : Microsoft.SystemCenter.CollectAlerts
    Instance    :
    Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: HealthService
    Event Category: None
    Event ID: 2115
    Date:  3/11/2010
    Time:  11:30:39 AM
    User:  N/A
    Computer:
    Description:
    A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
    Workflow Id : Microsoft.SystemCenter.CollectPerformanceData
    Instance    : yksc1s3.ehit.org
    Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: HealthService
    Event Category: None
    Event ID: 2115
    Date:  3/11/2010
    Time:  11:31:18 AM
    User:  N/A
    Computer:
    Description:
    A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
    Workflow Id : Microsoft.SystemCenter.CollectEventData
    Instance    :
    Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: HealthService
    Event Category: None
    Event ID: 2115
    Date:  3/11/2010
    Time:  11:31:18 AM
    User:  N/A
    Computer:
    Description:
    A Bind Data Source in Management Group  has posted items to the workflow, but has not received a response in 61 seconds.  This indicates a performance or functional problem with the workflow.
    Workflow Id : Microsoft.SystemCenter.CollectSignatureData
    Instance    : yksc1s3.ehit.org
    Instance Id : {A18674C9-F1A9-98DA-3B94-DD88EAE278FB}
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    This is caused by a high number of sql queries to the Datawarehouse database. The work around is to add an override for the Event Data Collector rule in the Data warehouse connection server scope.
    The Execution Attempt Timeout Interval Seconds property was changed from 0 to 6 and the Max Execution Attempt Count was set from 0 to 10. Restart the System Center service on the RMS and any gateway servers.

    Posted by DaFixer @ 9:25 pm

    Tags: , ,

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.