Network Management

Discovery fails on import phase

Discovery fails during the import phase. The following can be found upon checking the Core.BusinessLayer.log file. (SWDiagnostics->LogFiles->Orion->Core.BusinessLayer.log)

First published date

10/22/2018 7:34 PM

Last published date

4/14/2026 8:19 PM

Overview

If you have a discovery is failing when it gets to the import phase, check the Core.Businesslayer.log at the time of the issue for the below error,

ERROR SolarWinds.Orion.Core.Common.CoreErrorHandler - Error occured on Business Layer call. Type: System.Data.OleDb.OleDbException
ErrorCode: '-2147467259'
Errors: 'System.Data.OleDb.OleDbErrorCollection'
Message: 'Unspecified error'
Data: 'System.Collections.ListDictionaryInternal'
InnerException: ''
TargetSite: 'Void .ctor(System.Data.OleDb.OleDbConnectionString, System.Data.OleDb.OleDbConnection)'

 

Product section

Orion Platform

Resolution

The JET error lets you know that it is a issue with the *JET files in Windows/Temp. Stop the services and the clear the *JET files from Windows temp and restart the services and test again to see if it them completes with no issues.

Orion Platform 2015.1.2 Hotfix 2 is supposed to address the issue, but you may still need to clear out the *JET files after applying the hotfix. Issue can also be caused by the Businesslayer crashing so check the businesslayerhost.log to verify that they is no issues.

  1. Stop Orion services.
  2. Go to C:\Windows\Temp.
  3. Check temporary directories and remove all .tmp files beginning with JET.
  4. Start Orion services.

See also: Discovery import fails on SAM+VMAN Free polling Engine