Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > IP Address Manager (IPAM) > IPAM scan error: Unable to update database with subnet scanner state

IPAM scan error: Unable to update database with subnet scanner state

Updated June 30, 2017

Overview

IPAM scans are not running and the following errors are found in the IPAM business layer log:

ERROR SolarWinds.Orion.Core.SharedCredentials.CredentialDAL (null) - Unable to find credential with ID = 5, owner = IPAM and credentialType = SolarWinds.IPAM.Storage.Credentials.WindowsCredentialDataObject

ERROR SolarWinds.IPAM.ScanningEngine.ScanStateManager (null) - Unable to update database with subnet scanner state. Will wait 20 seconds then retry.
SolarWinds.Orion.Core.SharedCredentials.Exceptions.CredentialNotFoundException: Unable to find credential with ID = 5, owner = IPAM and credentialType = SolarWinds.IPAM.Storage.Credentials.WindowsCredentialDataObject

Environment

IPAM 4.5.0

Cause 

A device being scanned for DHCP data has a missing or corrupt credential assigned to it OR the node in question was removed from the Orion suite, along with it's credential, but was not removed from IPAM.

 

Any node that is removed from the Orion suite that is being polled by IPAM must also be removed from the IPAM module. If it is not removed, the above issue can occur as the system is trying to find data that is no longer present.

Resolution

Create or modify the account in use if it's just the account that is affecting it, otherwise remove the node or device from IPAM to resolve the issue.

 

Last modified
13:48, 2 Aug 2017

Tags

Classifications

Public