Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM restarting module engine service due to out of memory error

VNQM restarting module engine service due to out of memory error

Created by Matthew Lamb, last modified by MindTouch on Jun 23, 2016

Views: 777 Votes: 0 Revisions: 9


This article describes an issue that can occur with the Orion Module Engine Service restarting due to the VNQM module crashing from an out of memory exception error.

The following error message is seen in the BusinessLayerHost.log:

ERROR SolarWinds.BusinessLayerHost.PlugInstanceSeparateProcess - Instance C:\Program Files (x86)\SolarWInds\Orion\VoIP

Monitor\SolarWinds.Orion.IpSla.NusinessLayer.dll.congif - ProcessID:9468 doesn't exists anymore

ERROR SolarWinds.Common.Ultility.ScheduledTask - CheckPlugins threw and exception.

System.InvalidOperationException: Instance C:\Program Files (x86)\SolarWins\Orion\VoIP Monitor\SolarWinds.Orion.IpSla.BusinessLayer.dll.config


VNQM 4.2 and later


This is due specifically when an Avaya Call Manager environment is configured to send its call records (CDR) and its call metric information (RTCP) to the VNQM server, but the Call Manager was never added into VNQM or was removed.

What happens is the VNQM collector is still receiving the CDR\RTCP data, but has nowhere to place the data. Such data is normally dropped and not collected, but excessive amounts of data arriving to the VNQM server causes the data to be loaded into the memory allocated for VNQM through the Orion Module Engine service until it can be parsed through and compared against the database. Eventually, that amount of data is going to exceed the limits in place for the module's usage and causes it to run out of memory. At that point, the module crashes resulting in the Orion module engine service restarting in an attempt to restart the VNQM module.

Last modified