question

MichaelEriksson-2831 avatar image
0 Votes"
MichaelEriksson-2831 asked KaelYao-MSFT edited

OLS User Store - Query

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.GetAttribute[T](Dictionary`2 attributes, String attributeName, Boolean isMandatory, T defaultValue, Func`2 parseMethod)
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetAttribute[T](String attributeName, Boolean isMandatory, T defaultValue, Func`2 parseMethod)
at Microsoft.Office.Datacenter.Monitoring.ActiveMonitoring.Recovery.AttributeHelper.GetDouble(String attributeName, Boolean isMandatory, Double defaultValue, Nullable`1 minimum, Nullable`1 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

office-exchange-server-administrationmsc-operations-manageroffice-exchange-server-itpro
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi, Michael.

Due to the limit of our forum, we are not able to help you find the root cause of the problem.

Since Exchange has self-recovery capabilities, it will manage to do the recovery first once it discovers the health set is in unhealthy status.
As you mentioned in the post, after some time the error seems to heal it self.

If currently you don't have any actual issues with the Exchange server, I would agree with the suggestions to ignore the alert.
It is also recommended to keep your Exchange server up to date.
If there are Microsoft documentations on this topic published, I will keep you informed as soon as possible.

In addition, I have added the "msc-operations-manager-general" tag which is used for SCOM related questions to this question.
If you would like to disable the alert in SCOM as a workaround, it may help you get some suggestions.

Thanks for your understanding.

0 Votes 0 ·

0 Answers