Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM Business Layer failed to start

VNQM Business Layer failed to start

Updated June 23, 2016

Overview

 

The following message appears after upgrading VNQM to 4.2.4. 

 

VNQM Business Layer" failed to start on [Servername]. Please restart the Module Engine service on [Servername]

 

When this happens, issues such as adding a Call Manager, IPSLA operation in unknown status will occur. This is because the IPSLA business layer is failing.

 

Looking at IPSLA BusinessLayer log, it will show these error messages.

 

2016-06-16 19:01:12,099 [7] ERROR BusinessLayer.Plugin (null) - IP SLA Monitor service [SERVERNAME] failed to start. 

System.ArgumentException: An item with the same key has already been added.

   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)

   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)

   at SolarWinds.Orion.IpSla.BusinessLayer.ServiceMonitor.UpdateEngines()

   at SolarWinds.Orion.IpSla.BusinessLayer.ServiceMonitor.Start()

   at SolarWinds.Orion.IpSla.BusinessLayer.VoipBusinessLayerPlugin.Start()

2016-06-16 19:31:10,455 [Scheduler] ERROR SolarWinds.Common.Utility.ScheduledTask (null) - OptimizePollingJobExecution threw an exception.

System.ObjectDisposedException: Cannot access a disposed object.

Object name: 'SolarWinds.Orion.IpSla.Polling.Poller'.

 

 

Environment

  • VNQM 4.2
  • VNQM 4.2.X
  • VNQM 4.4.x

 

Cause 

 

  • Either a dll was improperly placed in the correct directory or in an additional directory, or the voipjobinfo table has duplicate entries.
  • Error in the ipsla.businesslayer.log is indicative that it is attempting to process a job that is either missing or duplicated from the voipjobinfo table in the database.

Resolution

 

1.  Stop all Orion services on all pollers

2. Backup your SQL Database before making any changes to the database.

3. Use the steps to run following SQL query  Running SQL query Orion Database Manager 

 

Truncate Table VoipJobInfo

 

4. Reinstall rebuild Solarwinds Collector on all pollers

5. Reinstall rebuild Solarwinds Job Engine v2 on all pollers

6. Reinstall the JobEngine.msi on all pollers

7. Start all Orion Services on all pollers

Please make sure everything is running 

 

 

 

Last modified
07:05, 3 Jul 2017

Tags

Classifications

Public