Unable to run network discovery on additional poller

11/1/2018 9:19 PM

4/5/2022 1:46 PM

Network discovery cannot be run on the Web Console when selecting the additional poller as the engine.

The following error messages may be found in the Orion website logs:(C:\Programdata\Solarwinds\Logs\Orion\OrionWeb.log)

WARN  Orion_Discovery_Default - Discovery profile message is not localized by website: Could not start / store discovery job: 104

 WARN  Orion_Discovery_Default - Discovery profile message is not localized by website: A Network Discovery job has failed to complete.\r\nState: Failed\r\nProfile id: 116.\r\n
 The Job Scheduler is reporting the following error:\r\nSolarWinds.JobEngine.WorkerProcess.JobExecutionException: System.Exception: Unable to deserialize job description. 
 ---> System.Runtime.Serialization.SerializationException: Error in line 0 position 0. 
 Element 'http://schemas.datacontract.org/2004...escriptionBase' contains data from a type that maps to the name 
 'http://schemas.solarwinds.com/2008/D...JobDescription'. The deserializer has no knowledge of any type that maps to this name. Consider using a DataContractResolver 
 or add the type corresponding to 'DeviceStudioDiscoveryPluginJobDescription' 
 to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding it to the list of known types passed to DataContractSerializer.

 

WARN  Orion_Discovery_Default - Discovery status is undefined (empty)

Network Performance Monitor

This can be caused by a firewall blocking communication.

Please verify that all required ports are open on any firewalls over pollers or devices in between.

Refer to Port Requirements of SolarWinds Products