As the title indicates, we've been getting these error messages in our system log from various event services for as long as I can remember:
MxEventAgentService:Error running eventagent check
It is JobId 0 (makes sense, as it is coming from one or the other of our event agents) and has no additional info.
Also, our event services seem to "lock up" and stop running at various points, and I can't help but wonder if this message is related. We'll see this message about 40 times a day from various event services, but usually only get one or two lock-ups per week. Still, it is a serious issue when role requests aren't processed in our Production environment because an event agent service just stops. Once we stop/start the service it will resume processing as normal.
Are we doing something wrong? Each of our event agent services has 4-5 event agents assigned to it. Is this too many? They are all reading different tables, I am not sure why this would be a problem, but maybe it is just overloaded?
Any similar experiences out there, hopefully with some sort of solution?
We thought of using an event agent to monitor a table and run a job to process it. Because the event agents have a polling interval before running the job, we felt that it would be simpler to just schedule the job itself to poll the table every x minutes. I couldn't quite understand the purpose of event agents for monitoring tables. Perhaps we have a gap in our understanding of them...
Add a comment