In my environment, we have 2 SCOM 2012 server and in one of them have following error:

Log Name:      Operations Manager
Source:        Health Service Modules
Event ID:      31552
Task Category: Data Warehouse
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      X.Domain.com
Description:
Failed to store data in the Data Warehouse.
Exception 'SqlException': Sql execution failed.
Error 777971002, Level 13, State 1, Procedure EventProcessStaging, Line 398, Message: Sql execution failed. 
Error 1205, Level 13, State 56, Procedure EventProcessStaging, Line 245, Message:
Transaction (Process ID 67) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.
Rerun the transaction. 

One or more workflows were affected by this.  

Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance 
Instance name: Event data set 
Instance ID: {33BCA1DB-D2DB-1830-A489-C5C094BFF242} 
Management group: Group

How can resolve it?

Thanks

Hi There,

These events are a bit normal if you see them once in a while. But if you see them very frequently then you will need to troubleshoot.

So i will require some answers here.

1. Is your SQL in the same SCOM server or is it in a remote server ?

2. Are the databases kept in a VM disk or SAN ?

you may refer to the following post

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/595796fc-e778-4e2a-afff-3b5ec53fcc1e/opsmgrscom-transaction-was-deadlocked-on-lock-resources-with-another-process-and-has-been-chosen?forum=sqldatabaseengine
Roger

Hi,

this error show sometimes.

1-  my SQL server is in remote server and both SCOM Server are separated. 
2- Operational Database and Data warehouse are in VM disk.

thanks

Hi There,

For performance reasons to avoid these issues, MS has recommended to keep the databases on a physical disk and not a VM disk.

Below is the screenshot for the same.

https://technet.microsoft.com/en-us/dn249696

I would suggest if you see more of these events you will need to migrate the db's to a physical disk. If you see this very rarely you can ignore it.