4,608 questions
Since it is not supported to edit the database in anyway. You only option is to contact Microsoft Support and have them assist you.
The SQL Store Procedure "spEPProcessMalwareMessage" is creating huge Deadlock.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 55.00000000000001%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER1%3C/text%3E%3C/svg%3E)
Raj-1602
26
Reputation points
Last few days I observed, the SQL Store Procedure "spEPProcessMalwareMessage" is creating huge Deadlock as a result my MECM Database is increasing size that is not manageable.
The warning message has given below:
Record 265 returned a 'deadlock' return code and failed processing with error 1205: ERROR 1205, Level 13, State 52, Procedure spEPProcessMalwareMessage, Line 52, Message: Transaction (Process ID 342) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Could anyone please help to sort out the issue. Thank you.
Microsoft Security Intune Configuration Manager Other
{count} votes
-
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator2023-12-10T11:32:25.7433333+00:00 To be able understand the deadlock, you need to get hold of the deadlock XML. You can use this query to see the deadlocks and when they occurred:
; WITH CTE AS ( SELECT CAST(event_data AS xml) AS xml FROM sys.fn_xe_file_target_read_file( N'system_health*.xel', DEFAULT, DEFAULT, DEFAULT) WHERE object_name = 'xml_deadlock_report' ) SELECT xml.query('/event/data[1]/value[1]/deadlock[1]'), xml.value('/event[1]/@timestamp', 'datetime2(3)') AS timestamp_utc FROM CTE ORDER BY timestamp_utc DESCNote that the timestamps are in UTC, so you need to make a mental conversion to your local time zone.
Share one of the deadlocks, and maybe we can get an idea of what is going on.
Deadlocks as such does not result in database growth, but I can see the database could grow, if it is a cleanup procedure that fails to run due to the deadlock.
Then again, the procedure name suggest that's the procedure is doing something else. Maybe you all of a sudden has gotten a lot of malware messages?
I should add that my speciality is SQL Server as such, and I know nothing about MECM. If MECM specialists who see this can can fill what spEPPRocessMalware is and other application details, that could help.
Sign in to comment