Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
This article goes over an issue that occurs in NPM 11.5+ during a discovery where it fails with this error in the Web Console:
An error while processing the results has occured. See discovery log for more details
And this error that occurs in the Core.BusinessLayer.logs:
ERROR SolarWinds.Orion.Core.Common.CoreErrorHandler - Error occured on Business Layer call. Type: System.Data.OleDb.OleDbException
Message: 'Unspecified error'
TargetSite: 'Void .ctor(System.Data.OleDb.OleDbConnectionString, System.Data.OleDb.OleDbConnection)'
StackTrace: ' at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at SolarWinds.Orion.Core.Common.DALs.DiscoveryDatabaseDAL.OleDbHelperExecuteScalar(String query)
at SolarWinds.Orion.Core.Common.DALs.DiscoveryDatabaseDAL.GetInterfaceTypeDescription(Int32 ifType)
at SolarWinds.Orion.Core.Discovery.DataAccess.DiscoveryDatabase.LoadInterfacesAndVolumesForNode(DiscoveryNode discNode, IEnumerable`1 plugs)
at SolarWinds.Orion.Core.BusinessLayer.CoreBusinessLayerService.GetVolumesAndInterfacesForDiscoveryNode(DiscoveryNode discoveryNode)
at SyncInvokeGetVolumesAndInterfacesForDiscoveryNode(Object , Object , Object )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object inputs, Object& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)'
Source: 'Microsoft JET Database Engine'
NPM version 11.5+
This issue occurs when Orion is either unable to communicate with or has lost connection to the OleDB on the server it is installed on. Why this occurs are generally one of 4 possibilities:
The local NETWORK SERVICE requires Read\Write to this directory to allow the Orion services to access it. If for any reason that account and rights are not present, this issue can occur.
The directory has a file limit of 65536 and anything over that causes problems accessing or utilizing files within until it is cleaned up or reduced in file count.
The Orion Module Engine Service contains the plugins for all the Orion applications and uses a fixed memory limit. If one or more of the plugins are consuming near or at the cap for allocation, other plugins will have resource conflicts with what is left.
Orion Core HotFix 6 has some corrections to the causes above and it is recommend that this is applied before proceeding. You can find it here: Download
You can also upgrade to NPM 11.5.3 as it contains the above hotfix.
If the hot fix or upgrade does not correct the issue, please follow the following steps:
Note: These steps increase the memory and CPU usage on the server from a small to medium amount. Be prepared to expand or add resources as needed.