Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Performance counters can crash JobEngine worker process in SAM

Performance counters can crash JobEngine worker process in SAM

Updated: 3-8-2017

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.

Environment

  • SAM
  • JobEngine

 

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.

 

 

Last modified

Tags

Classifications

Public