Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Topology Calculator crashes immediately after initialization

Topology Calculator crashes immediately after initialization

Created by Daniel Polaske, last modified by Caroline Juszczak on Jan 29, 2019

Views: 1,013 Votes: 0 Revisions: 11

Updated July 4, 2016


In the process of troubleshooting topology issues, you may find that the Topology Calculator is not updating the database's existing topology data. 


This can be verified in the [dbo].[TopologyConnections] table in the LastUpdateUtc column, which will display a large number of rows at some date in the past which indicates when the last time the Topology Calculator was successfully run.


When manually running the SolarWinds.Orion.Topology.Calculator.exe file from %SYSTEMDATA%\Program Files (x86)\Solarwinds\Orion\, you may find that the executable starts and crashes almost immediately afterwards.  This can be observed in the Task Manager, the process will start and run for about 30 seconds and then crash.


The following behavior is seen in the SolarWinds.Orion.Topology.Calculator.exe.log file:


INFO  TopologyCalculator.Program - Topology calculator executed.
*** Assembly SolarWinds.Orion.Common, Version=, Culture=neutral, PublicKeyToken=316e86daa515e407, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Orion.Core.Common, Version=2015.1.25300.8259, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.InformationService.Contract2, Version=2015.1.1.6134, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
*** Assembly SolarWinds.Orion.Pollers.Framework, Version=2015.1.25300.8197, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
ERROR SolarWinds.Orion.Pollers.Framework.ObjectTypeFactoryBase`1 - Unable to find type identifier 'ComplementaryLinksSelectorL3' in list of SolarWinds.Orion.Core.Topology.Calculation.OrionDataLoadersFactory known types
*** Assembly SolarWinds.Orion.Topology.Framework, Version=2015.1.1.8, Culture=neutral, PublicKeyToken=null, .NET version v4.0.30319 ***
DEBUG SolarWinds.Orion.Topology.Framework.Features.Sysname+ValidatorByLength - Input Sysname 4 rejected because of insufficient length. Required length is 2.
ERROR SolarWinds.Orion.Pollers.Framework.ObjectTypeFactoryBase`1 - Unable to find type identifier 'PhysicalAddressMapFeatureProvider' in list of SolarWinds.Orion.Core.Topology.Calculation.OrionFeatureProviderGeneratorsFactory known types
ERROR TopologyCalculator.Program - Failed, exception: System.Collections.Generic.KeyNotFoundException: Unable to find type PhysicalAddressMapFeatureProvider
   at SolarWinds.Orion.Pollers.Framework.ObjectTypeFactoryBase`1.CreateObjectInstance(String typeIdentifier)
   at SolarWinds.Orion.Core.Topology.Calculation.OrionFeatureProviderGeneratorsFactory.Create(String description)
   at SolarWinds.Orion.Core.Topology.Calculation.TopologyCalculationEngine.<>c__DisplayClass31.<Calculate>b__2e(ProviderConfig entry)
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at SolarWinds.Orion.Core.Topology.Calculation.TopologyCalculationEngine.Calculate()
   at TopologyCalculator.Program.Main(String[] args)
INFO  TopologyCalculator.Program - Topology calculator finished. Time elapsed: 00:00:30.3440121



All Orion NPM 11.5.2 environments (Core 2015.1.25300.0) with NPM 11.5.2 and Core HotFix 3 installed


This issue is known and caused by a missing/corrupted or incorrect SolarWinds.Orion.Core.Topology.dll.

Specifically, the fix below would bring Orion.Core.Topology and Crion.Topology.Framework to the same level.


The best option to fix this would be to upgrade to NPM 12. However, if that is not possible, install NPM 11.5.2 Core HotFix 6.




Last modified