Hi,
To solve this issue, we may refer to the steps in this blog. In case of any data loss, please backup the data before proceeding.
Regards,
Alex
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello All, Good day, We are observing the below alert from SCOM 2019 reporting cum management server . "Data Warehouse event data writer process failed to perform maintenance operation." Could you please help me in solving this issue. Thanks in advance!! Regards, Aswin
Hi,
To solve this issue, we may refer to the steps in this blog. In case of any data loss, please backup the data before proceeding.
Regards,
Alex
Hi , There could be multiple causes for your issue. Please have a look at the following article from Kevin Holman: https://kevinholman.com/2010/08/29/the-31552-event-or-why-is-my-data-warehouse-server-consuming-so-much-cpu/
The most common issues causing the 31552 events seen are:- A sudden flood (or excessive sustained amounts) of data to the warehouse that is causing aggregations to fail moving forward.- The Exchange 2010 MP is imported into an environment with lots of statechanges happening.- Excessively large ManagedEntityProperty tables causing maintenance to fail because it cannot be parsed quickly enough in the time allotted.- Too many tables joined in a view or query (>256 tables) when using SQL 2005 as the DB Engine- Poor SQL performance issues (typically disk I/O latency)- Using SQL standard edition, you might see these randomly at night, during maintenance as online indexing is not supported using SQL standard edition.- Messed up SQL permissions- Too much data in the warehouse staging tables which was not processed due to an issue and is now too much to be processed at one time.- Random 31552’s caused my DBA maintenance, backup operations, etc..
Marius ENE (https://mariusene.com/ )