nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Event Log Message

dotexy

Error Opening MainTaskDataReader Transaction (Process ID 72) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Please does anybody knows what this message means?

Find more posts tagged with

Accepted answers

All comments

mark_wiggans

Some other process was occurring on the DB when the MainTaskDataReader tried to access it. Process ID 72 was the transaction that was deadlocked.

dotexy

Thanks a lot. I got the clue..

tdanner

When I've seen these messages before, the cause has usually been running the SolarWinds Alerting Engine service on more than one box. One instance of that service is sufficient to process all of the alerts, so you can make the messages go away if you just stop and disable all but one copy of that service.

jtimes

When I've seen these messages before, the cause has usually been running the SolarWinds Alerting Engine service on more than one box. One instance of that service is sufficient to process all of the alerts, so you can make the messages go away if you just stop and disable all but one copy of that service.

So if I turn off the SolarWinds Alerting Engine on my 7 other pollers will they still process the Basic alerts independently

tdanner

Yes, basic alerts will still be processed normally. The Alerting Engine service only handles Advanced Alerts.

jtimes

very cool, do you think you guys could script something for us folks that have multiple polling engines, just so we don't have to do this manually on every one, every time the server gets re-started for OS patches... same deal with the Syslog service...and Trap service...

Come to think of it, can I just un-install those services on polling engines where they are not needed???

dotexy

The solarwinds alerting engine service is running on just a box and i have just one polling engine.

Does that message affect solarwinds from working properly?

How do i get to solve this problem?

dotexy

Please i don't get what Process ID 72 means. How and where can i search for the meaning on my box? Also how do i rerun the application?

WINNT

I have thousands of these alerts since I've upgraded to v8.5.1 SP1. I am hoping that Orion is "rerunning the transaction" or else data is not getting written to SQL. I also get hundreds of these Alerting Engine errors that tells me the alerting process has hung:

Event Type: Error
Event Source: AlertingEngine
Event Category: None
Event ID: 0
Date:  11/15/2007
Time:  4:39:46 AM
User:  N/A
Computer: ORION
Description:
2007-11-15 04:39:46,921 [MainTaskThread] ERROR All - Error in SetupMainDBConnection Object reference not set to an instance of an object.

I will need to set up a SysLog event to restart the alerting service when these are encountered.