Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > 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


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()>


All NPM versions


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