none
Event ID: 8000 and Event ID:_31552 issue.

    Question

  • Hi

    We have installed the new additional management server(SCOM 2007 R2) in our environment and getting the below errors.

    Event Type:    Error
    Event Source:    Health Service Modules
    Event Category:    Data Warehouse
    Event ID:    31552
    Date:        8/21/2013
    Time:        8:30:28 AM
    User:        N/A
    Computer:    IND-MS4
    Description:
    Failed to store data in the Data Warehouse.
    Exception 'SqlException': A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    One or more workflows were affected by this.  

    Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectEventData
    Instance name: IND-MS4.lab.com
    Instance ID: {C49DE88D-B3D1-27BB-C8C2-889030EA829F}
    Management group: mg_lab

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

    Event Type:    Warning
    Event Source:    HealthService
    Event Category:    Data Publisher Manager
    Event ID:    8000
    Date:        8/21/2013
    Time:        9:00:58 AM
    User:        N/A
    Computer:    IND-MS4
    Description:
    A subscriber data source in management group mg_lab has posted items to the workflow, but has not received a response in 32 minutes.  Data will be queued to disk until a response has been received.  This indicates a performance or functional problem with the workflow.
     Workflow Id : Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData
     Instance    : IND-MS4.lab.com
     Instance Id : {C49DE88D-B3D1-27BB-C8C2-889030EA829F}
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Assist us to resolve the issue.


    Donald D'souza (http://donald-scom.blogspot.com/)

    Wednesday, August 21, 2013 3:11 PM

Answers

  • Looks like the database is offline or the management server just can't connect to it for some reason - maybe a network related issue...

    Open up SQL Management Studio and take a look at the SQL Server logs on your database for more information. If you can remotely connect, then that's good - and let us know if you find any connection errors source from a Management Server.

    Maybe a little more context around the issue would help as well - like if other MG processes are running, and health indicators in the console, etc...


    Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

    Friday, August 23, 2013 7:13 AM
    Moderator

All replies

  • Looks like the database is offline or the management server just can't connect to it for some reason - maybe a network related issue...

    Open up SQL Management Studio and take a look at the SQL Server logs on your database for more information. If you can remotely connect, then that's good - and let us know if you find any connection errors source from a Management Server.

    Maybe a little more context around the issue would help as well - like if other MG processes are running, and health indicators in the console, etc...


    Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

    Friday, August 23, 2013 7:13 AM
    Moderator
  • Hi Jonathan

    Yes You are right the MS server unable to communicate with the DW. I have fixed this issue by adding the DW server name in the host file and communication started.

    Regards

    Donald Dsouza


    Donald D'souza (http://donald-scom.blogspot.com/)

    Tuesday, August 27, 2013 11:19 AM
  • Hi Jonathan

    Yes You are right the MS server unable to communicate with the DW. I have fixed this issue by adding the DW server name in the host file and communication started.

    Regards

    Donald Dsouza


    Donald D'souza (http://donald-scom.blogspot.com/)

    Donald - the answer was marked incorrectly, so I fixed that.

    Also, you just tossed a needle in a haystack by making a host file entry. If someone needs to troubleshoot name resolution in the future, they will need to know there is a host file entry being used somewhere. The way to resolve this is the update DNS with the correct hostname. In most implementations, where AD maintains DNS, this would happen automatically. But sometimes you may need to contact your network services team to make the name change in DNS.


    Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

    Tuesday, August 27, 2013 4:09 PM
    Moderator