Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Discovery fails on import phase

Discovery fails on import phase

Table of contents


If you have a customer that the 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,

2015-09-15 18:01:18,545 [189] 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)'


All NPM versions



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.


Last modified
22:14, 22 Mar 2017