OLS User Store - Query

Question

Is there anybody out there that know anything about this. We've had two cases with MS during the last couple of years and I have frequently googled this mysterious alert to try and fix it. The only answer, from MS as well as Google, seem to be "ignore it". My problem is that I have a hard time doing that, at least before I know exactly what it is and if it can be fixed.

If it is just to be ignored, why do Config Manager classify it like a critical error and not just info or warning? In Exchange 2013 it didn't exist, at least I didn't see it, but I've come a cross it in both 2016 and 2019. The error seems to heal it self, but before that happens it has already triggered an alert in our Operations Center that picks up the phone and start calling the technician on call.

The error in SCOM says:

Maintenance workitem "OlsQuery.Maintenance.Workitem" (ID: 2045954113) has failed. Health Manager has detected it is either set to run once and failed, or has been failing consistently. Maintenance workitem failure could cause monitoring gap and should be investigated.

The error message from the last result is:
System.FormatException: Input string was not in a correct format.
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Double.Parse(String s)
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetAttributeT
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetAttributeT
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetDouble(String attributeName, Boolean isMandatory, Double defaultValue, Nullable1 minimum, Nullable1 maximum)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.OlsQuery.FailureRateProbeSettings..ctor(WorkDefinition workDefinition, String prefix)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.OlsQuery.FailureRateProbe.AddWorkDefinitions(MaintenanceWorkItem maintenanceWorkItem)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.OlsQuery.OlsQueryDiscovery.CreateMonitoringContexts(LocalEndpointManager endpointManager)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.OlsQuery.OlsQueryDiscovery.DoWork(CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<ExecuteAsync>d__b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<StartExecutingAsync>d__7.MoveNext()

Knowledge: http://technet.microsoft.com/en-us/library/ms.exch.scom.OLS User Store - Query(EXCHG.150).aspx?v=15.2.792.3

The link of course doesn't work... This must be the least documented error there is on a Microsoft product.

I hope some of you clever men and women can enlighten me, I would be very grateful.

Regards

Michael