Error XPCORuleSystemManager Failed to enqueue event. Failed to lookup event in VMO

MIP
, , , ,
1

Hi all.

I have developed some plugins (client and server). After upgrading to 2019R3 Corporate, many errors like this occur:

2020-02-08 21:00:40 UTC + 01: 00 XPCORuleSystemManager error The event cannot be queued. Unable to search for event in VMO

My EventServer is full of these errors. The error occurs every two seconds.

What does this error mean? What are the effects?

Thank you.

Ciao.

Gigi

2

I have not seen this exact error before.

If you disable your plugin as a test, does the errors still show in the logs?

My guess is that a rule that you have set up in the Management Client never triggers because an event is missing or because of a communication issue between Event Server and Management Server. Will you be able to identify which rule might cause this? If you disable rules as a test you might be able to figure that one or two of them cause the issue. You might be able to disable them all and re-enable them and see when the issue starts happening. For efficient testing I think you wil need to restart the Event Server service when you have disabled or enabled a rule.

3

Hi Bo.

I have no custom rules. In any case I have disabled all rules and, after restarting event server, no more errors in log.

So, certainly, my plugin is cause of this error, but i can’t understand why.

Errors begin where my background plugin starts to create event. These errors started after updating to 2019R3.

Some idea ?

Thanks.

Ciao.

Gigi

4

Can you find which one rule cause the issue? I have an idea you can enable all rules except one, I would like to know the content of that rule. My primary suspect would be that if you have a rule that uses the event that your background plugin creates, then it is the one rule you need to disable.

If there is no such rule please still disable and enable them one by one to see if you can find one that causes this. Let me know the content of that rule (if there is one rule that causes this).

Please tell me how the background plugin creates the event, a snippet of your code might be the best way to explain this.

5

Hi Bo.

I have no rules. For my plugins I don’t use rules. Only default milestone rules are configured.

After some test, I’m sure that errors starts when my backgroud plugin start to push new events.

Thanks.

Ciao.

Gigi

About my code:

	...
 
	EventHeader eventHeader = new EventHeader()
	{
		ID = Guid.NewGuid(),
		Class = "Operational",
		Type = "MyCustomType",
		Timestamp = DateTime.Now,
		Message = message,
		Name = controllerName,
		Source = new EventSource
		{
			FQID = zoneItem.FQID,
			Name = zoneItem.Name
		},
		CustomTag = customTag
	};
 
	Vendor v = new Vendor
	{
		Name = partitionFieldInfo
	};
 
	AnalyticsEvent eventData = new AnalyticsEvent
	{
		EventHeader = eventHeader,
		Location = locationFieldInfo,
		Vendor = v
	};
 
	EnvironmentManager.Instance.SendMessage(new Message(MessageId.Server.NewEventCommand) { Data = eventData });
	EventServerControl.Instance.ItemStatusChanged(zoneItem);
	
	...
6

One idea..

Can you verify that you still have an AnalyticsEvent configured in Management Client with the name (name in variable message)?

The idea is that if the analytics event is missing it can cause the issue. The analytics event could have been removed while the upgrade was performed.

7

Hi Bo.

We found the bug: in public override Collection GetKnownEventTypes(System.Globalization.CultureInfo culture) we had registered an incorrect Kind for my context. After removing it, there were no more errors in the log

Thanks.

Ciao.

Gigi