Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > IP Address Manager (IPAM) > IPAM - Knowledgebase Articles > IPAM Scanjob not running Missing GroupID on IPAM_Group table

IPAM Scanjob not running Missing GroupID on IPAM_Group table

Updated: November 1, 2017

Overview

This article provides a workaround to situations when the Subnet scan/Scan job does not work in IPAM.

Environment

  • IPAM 4.5.1 and up

Cause 

Missing a GroupID on IPAM_Group and it's still added on DHCP and DNS Server.

 

2017-09-12 13:37:38,710 [STP DatabaseProcessing Thread #38275] ERROR SolarWinds.IPAM.ScanningEngine.JobProcessor.JobProcessorBase`1 - Error occurred when processing DHCP results - serverGroupId: 100, serverNodeId: 2223
System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 188) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Resolution

  1. Verify that there are no Error on IPAM BL, IPAM Collector, and IPAM Jobs.
  2. Check to see if you have the following error in the Collector Logs.

 

2017-09-12 13:37:38,710 [STP DatabaseProcessing Thread #38275] ERROR SolarWinds.IPAM.ScanningEngine.JobProcessor.JobProcessorBase`1 - Error occurred when processing DHCP results - serverGroupId: 100, serverNodeId: 2223
System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 188) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.


SAMPLE
 

IPAM_Group = No GroupID 100
 

 

 

NodesData = ServerNodeId: 2223
 

 

  1. Check the database IPAM_Group and verify if GroupID 100 is not available.
  2. Check the nodeID 2223.
  3. Counter check it with IPAM if they are the same.
  4. Delete the DHCP Server on IPAM.
  5. Restart Services.
  6. Check the scan jobs to ensure it is now running.
  7. Re-add the DHCP Server and verify that the scan job works.

 

 

 

Last modified

Tags

Classifications

Public