Network Management

Ambiguous query results received from Service Directory for a service ServiceId

Solarwinds Configuration wizard SWIS error Ambiguous query results received from Service Directory for a service 'ServiceId: Core.BusinessLayer, ServiceLogicalInstanceId: engine:1, ServiceInstancePropertyFilters: isStreamed-False'

First published date

10/31/2022 8:06 AM

Last published date

11/25/2025 6:07 PM

Overview

While upgrading from 2020.x release to 2022.x a very small minority of customer encountered this error message at the end of Configuration Wizard. 
ERROR TaskAdapter - Error running task Orion.EnsureBusinessLayerIsAvailable Verifying that the SWIS service is available
SolarWinds.ConfigurationWizard.Common.ConfigurationException: Connection to Business Layer Service did not succeed.
Last error: Ambiguous query results received from Service Directory for a service 'ServiceId: Core.BusinessLayer, ServiceLogicalInstanceId: engine:1, ServiceInstancePropertyFilters: isStreamed-False'. ---> SolarWinds.ApiProxyFactory.TransientApiProxyException: Ambiguous query results received from Service Directory for a service 'ServiceId: Core.BusinessLayer, ServiceLogicalInstanceId: engine:1, ServiceInstancePropertyFilters: isStreamed-False'.
And following error in Solarwinds ServiceDirectory logs 
ERROR SolarWinds.ServiceDirectory.LocalCache.ServiceDirectoryLocalCache - (null) Could not write to a local cache persistent storage, will retry in 00:05:00.
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

 

Product section

Network Automation Manager

Cause

Unknown

Resolution

There error message will indicate which EngineID is affected. Apply the resolution on the affected EngineID only.
  • Open the Database Manager on the Orion server.
  • Click Add Orion Server
  • Expand the Orion database and look for the Engines table.
  • Shut down all Orion services using Orion Service Manager on the affected polling engine.
  • Rename the ServerName of the affected engine and change the ServerType to Additional.
  • Once renamed, rerun the Configuration Wizard, and it will create a new engine record in the Engines table.
  • Once the Configuration Wizard is done. transfer the nodes from the old engine to the new polling engine
  • After nodes are transferred, it is safe to delete the old polling engine record.
You may also encounter the same error when adding a node if the Additional Polling Engine (APE) is not on the same version as the Main Polling Engine (MPE).

If the above steps do not help to resolve the issue, then Perform a fresh Orion installation (uninstall and reinstall) on the same Windows server