Applications Systems

Performance counters can crash JobEngine worker process in SAM

You may encounter issues with crashing when polling performance counters for out-of-the-box templates with agentless polling in SAM. The polling method runs without issue until you access performance counters with out-of-the-box templates. When accessing the performance counters, you may receive an AccessViolation error and crash of the JobEngine worker process. The article includes potential solutions and debugging information.

First published date

11/15/2018 2:17 AM

Last published date

6/25/2020 9:22 PM

Overview

You may encounter issues crashes of the JobEngine worker process when polling performance counters. When accessing the performance counters, you may receive an AccessViolation error and crash of the JobEngine worker process.

A resolution or work-around is not available at this time. You can try rebuilding counters or restart the affected system. This has a chance of helping with the issue. You can also enable DEBUG logging to identify the system causing the error. See resolution steps for more information.

Product section

Server Application Monitor

Cause

Polling performance counters may encounter issues: an AccessViolation error displays and the JobEngine worker process crashes.

Resolution

A resolution is not available at this time. When a work-around is determined or fix in a release is available, this information will be updated at that time.

 

You can try rebuilding counters or restart the affected system. This has a chance of helping with the issue. For information on rebuilding performance monitors, see the Microsoft support site (https://support.microsoft.com) for information on your version of Windows Server. For example, the following articles may help (these links are to a third-party site and may change):

You can also turn on DEBUG logging per application on suspicious applications to help identify the system causing the error. Check the logs for the applications and locate which application does not generate a DEBUG log. A missing log means the JobEngine crashed before generating the log for that application, indicating the possible system/application with issues.

For information on enabling DEBUG logging, see the  Turn on application debugging for SAM article.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.