Microsoft Configuration Manager
TroubleshootingHow to Handle Configuration Manager Asynchronous Errors by Using Managed Code
In brief
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
What Intune admins need to know
No administrator action is required; this updates the documentation’s service classification.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
How to Handle Configuration Manager Asynchronous Errors by Using Managed Code
To handle a Configuration Manager error that is raised during an asynchronous query, you test the RunWorkerCompletedEventArgs parameter Error Exception property that is passed to the SmsBackgroundWorker.QueryProcessorCompleted event handler. If Error is not null, an exception has occurred and you use Error to discover the cause.
@@ -5,7 +5,7 @@ ms.date: 09/20/2016 ms.subservice: sdk ms.topic: how-to ms.collection: tier3-ms.service: microsoft-endpoint-configuration-manager+ms.service: configuration-manager --- # How to Handle Configuration Manager Asynchronous Errors by Using Managed Code To handle a Configuration Manager error that is raised during an asynchronous query, you test the `RunWorkerCompletedEventArgs` parameter [Error](/previous-versions/t1yswz5k(v=vs.90)) Exception property that is passed to the [SmsBackgroundWorker.QueryProcessorCompleted](/previous-versions/system-center/developer/cc143778(v=msdn.10)) event handler. If [Error](/previous-versions/t1yswz5k(v=vs.90)) is not `null`, an exception has occurred and you use [Error](/previous-versions/t1yswz5k(v=vs.90)) to discover the cause.