Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > SolarWinds runs out of memory caused by multiple swjobengineworker2.exe processes

SolarWinds runs out of memory caused by multiple swjobengineworker2.exe processes

Updated September 13, 2016

Overview

Orion NPM server running out of memory swjobengineworker2.exe.

Error in the JobEngine logs, located in:

<Volume>:\Documents and Settings\All Users\SolarWinds\JobEngine\Logs
ERROR:<WARN  SolarWinds.JobEngine.Engine.WorkerProcessWCFProxy - Kill failed
System.Management.ManagementException: Invalid namespace
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at SolarWinds.JobEngine.Engine.WorkerProcessWCFProxy.KillProcessAndChildren(Process parent)
   at SolarWinds.JobEngine.Engine.WorkerProcessWCFProxy.Terminate()>

Environment

All NPM versions

Detail

When trying to kill the swjobengineworker2.exe, the application tries to make a call the OS WMI instance to run the query ProcessWCFProxy.KillProcessAndChildren. This is failing with the error:  Invalid namespace.

To test the WMI, run the WBEMTEST tool from Microsoft and query the local WMI instance.

The WMI test failed to connect to the local machine

This is a OS error. Please contact Microsoft to help troubleshoot.

 

 

 

 

Last modified

Tags

Classifications

Public