Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion services crash with out of memory exception error

Orion services crash with out of memory exception error

Created by Chris Klinedinst, last modified by Caroline Juszczak on Apr 06, 2018

Views: 984 Votes: 1 Revisions: 13

Updated July 24, 2017

Overview

Orion services regularly crash and the following error is found in the application event log:

Application: SolarWinds.DataProcessor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
   at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
   at System.Net.ListenerAsyncResult.IOCompleted(System.Net.ListenerAsyncResult, UInt32, UInt32)
   at System.Net.ListenerAsyncResult.WaitCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Environment

All Orion Platform versions

Cause 

A memory fragmentation occurs in the services due to a large dataset.

Resolution

Perform the following steps to enable faster memory cleaning:

  1. Back up the Config file for the affected service and make sure the backup is placed outside of the Orion directory.  
  2. Navigate to the Config file for the affected service, for example, the SolarWindsInformationServiceV3 config file is found in: %:\Program Files (x86)\Solarwinds\Orion\Information Service\V3 and the file name is SolarWinds.InformationService.ServiceV3.exe.config
  3. Edit the Config file and add the <gcServer enabled="true"/> line in the runtime section:
    <runtime>
    <enforceFIPSPolicy enabled="false"/
    <gcServer enabled="true"/>
    </runtime>
  4. Save the file and restart the services.

Additional conditions under which you may want to enable gcServer mode

  • Minimum of 16 GB of RAM (for SWIS only), 32 GB and more if also enabled for Module Engine Service. You can expect to see faster processing time.
  • Minimum of 8 physical CPU cores. You can expect to see improvement in end-to-end response of services.

Also see: Enabling gcServer mode for selected services

 

Last modified

Tags

Classifications

Public