SCOM Dataware House Errors

Dev99 00 41 Reputation points

Hello Everyone,
I am getting errors on Both Management Server realated to Dataware House.

Can Any body guide.
Critical Errors shows in SCOM,Event 31557=Failed to obtain synchronization process state information from Data Warehouse database. The operation will be retried.
Exception 'SqlException': Login failed for user 'omaa'.

One or more workflows were affected by this.

Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.ManagedEntity
Instance name: Data Warehouse Synchronization Service
Instance ID: {923CB7DC-B2A7-FD8D-49BC-48E2F72D4E94}
Management group: SCOM
Event 2115:A Bind Data Source in Management Group IIAPSCOM has posted items to the workflow, but has not received a response in 324300 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.Windows.Server.10.0.Process.HealthStateSubscription.Rule
Instance Id : {BC45FA1C-C438-8435-3E8E-1AA0FE20541A}

Event 31561: Failed to enumerate (discover) Data Warehouse objects and relationships among them. The operation will be retried.
Exception 'SqlException': Login failed for user 'omaa'.

One or more workflows were affected by this.

Workflow name: Microsoft.SystemCenter.DataWarehouse.Discovery.StandardDataSet
Instance name: Veeam.Virt.Extensions.VMware.Report.DWDataSet
Instance ID: {42BCE0E0-B111-9699-E65F-5F51FEA4D462}
Management group: SCOM

Both management Server are critical state and the screenshots attached for error show in scom alerts.

can any one guide me...what am i missing ,,why i get performance related issue when scom is working good....

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,419 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Leon Laude 85,676 Reputation points

    Hi @Dev99 00 ,

    It appears that you're having performance/communication problems between your SCOM management server(s) and SCOM Data Warehouse, what changes have been done recently in your SCOM environment? Any account changes?

    I suggest first of all to follow the official documentation below that goes through one of your errors:

    Troubleshoot event ID 2115-related performance problems in Operations Manager

    Here's also a blog post about the exact same errors you're receiving:



    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Best regards,

  2. Dev99 00 41 Reputation points

    Getting this event after every second...

    Event: 4506= Data was dropped due to too much outstanding data in rule "Microsoft.Windows.Server.10.0.Process.HealthState.Collection" running for instance "Windows Process Monitoring (Management server Name)" with id:"{BEFB188A-9CC0-A740-5500-DDA767FFDF6B}" in management group "Management Group name...".
    and the same event for Microsoft.Windows.Server.10.0.Process.PerfMetrics.Collection

    What is WIndows server 10 Process..Bundle of errors on SQL Server side..

    but this error remove after flusing health state of SQL Server...
    but getting this event on SQL Server..

    An Account specified in the Run As Profile "Microsoft.SQLServer.2014.ReportingServices.RunAsProfile.Monitoring" cannot be resolved. Specifically, the account is used in the Secure Reference Override "SecureOverridecd28899d_061a_d964_1645_44d228760150".

    This condition may have occurred because the Account is not configured to be distributed to this computer. To resolve this problem, you need to open the Run As Profile specified below, locate the Account entry as specified by its SSID, and either choose to distribute the Account to this computer if appropriate, or change the setting in the Profile so that the target object does not use the specified Account.

    Management Group:
    Run As Profile: Microsoft.SQLServer.2014.ReportingServices.RunAsProfile.Monitoring

    0 comments No comments