Event ID 2115

[Leon1983]

0

 

Hi,

We are experiencing multiple instances of the above event ID on both of our SCOM management servers. On the RMS the below workflows are being referenced;

Microsoft.SystemCenter.CollectSignatureData

Microsoft.SystemCenter.CollectPublishedEntityState

Microsoft.SystemCenter.CollectEventData

Microsoft.SystemCenter.CollectAlerts

Microsoft.SystemCenter.CollectPerformanceData

Microsoft.SystemCenter.CollectDiscoveryData

On the second Management server on the below is being referenced;

Microsoft.SystemCenter.CollectDiscoveryData

 

I am led to believe this is indicating performance issues specifically with the operational Database and have followed this article to the best of my ability https://support.microsoft.com/en-us/help/2681388/how-to-troubleshoot-event-id-2115-related-performance-problems-in-operations-manager . I can also confirm that the most recent changes in our SCOM Infrastructure that may be affecting this are;

1.New Management server was added to the environment

2.SCOM Action Account had to have its password changed, which I followed the procedure as per this article http://thoughtsonopsmgr.blogspot.co.uk/2015/01/om12x-changing-passwords-om12x-service.html

3.Both the Operational and Data Warehouse Databases which almost full and only auto growing by 10MB at a time, so I have removed auto grow and sized both databases correctly, removing autogrow.

I also believe that excessive configuration churn is not taking place due to the presence of event ID's 21024 being promptly followed by 21025 or 21026 in the event logs as per the following article https://support.microsoft.com/en-us/help/2603913/how-to-detect-and-troubleshoot-frequent-configuration-changes-in-operations-manager

Is there anything else that I can check for on this?

Regards

Leon

[adurrant]

Hi Leon,

I'm experiencing the same issue, did you ever get this resolved? If so, would you care the share the resolution?