Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > Module Engine crashes due to Unhandled Exception caught in DPI Service Engine startup. Agent Messaging System initalization failed after retries: 25

Module Engine crashes due to Unhandled Exception caught in DPI Service Engine startup. Agent Messaging System initalization failed after retries: 25

Created by Andy Ng, last modified by Jamin Walters on Feb 10, 2017

Views: 1,743 Votes: 6 Revisions: 8

Overview

This article describes the issue when the Module Engine crashes and you receive this error:

Unhandled Exception caught in DPI Service Engine startup. Agent Messaging System initialization failed after retries: 25

 

The DPI.Businesslayer.log (C:\ProgramData\Application Data\Solarwinds\Logs\DPI\) also sends out this error message:

2015-12-31 15:34:06,483 [7] INFO  SolarWinds.DPI.BusinessLayer.DPIBusinessLayerPlugin - Agent Messaging System initalization failed, retries: 4
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/SolarWinds/AgentManagement/Messaging that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/SolarWinds/AgentManagement/Messaging' could not be found on your local machine.
   --- End of inner exception stack trace ---

 

AgentManagement.AMSProxy.log (C:\ProgramData\Application Data\Solarwinds\Logs\AgentManagement\) displays this error:

2015-12-31 15:32:56,656 [6] ERROR SolarWindsAMSProxy.Communications -  MessageCollection::GetMessages() - Exception [System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.CtorCharPtr(Char* ptr)
   at Message2MessageCLI(Message* msg)
   at SolarWindsAMSPersistenceCLI.MessageCollection.GetMessages(MessageDirection md)]

Environment

  • SAM version 6.2 and higher

Cause 

This issue occurs when Store.dat becomes excessive in size.

 

Resolution

  1. Check C:\ProgramData\SolarWinds\AgentManagement\Data\Store.dat if it continues to crash at 1,5GB of space.

  2. Move the file to your desktop or rename it. 

  3. Restart the Orion services.

 

Last modified

Tags

Classifications

Public