This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

IPAM Scan job Status question

scotthill over 8 years ago

In IPAM in the scan job status in IPAM settings, the status is "queued" and never changes. Scan trigger is automated. Last discovery shows the date probably when it was first set up.

When you chose a subnet and click on the Scan feature, it doesnt scan, it appears as if it just Qued up the scan job but wont ever run. Looks like there is multiple jobs in there as well.

Is that normal? Is that because they were queued up run automatically and never ran? How do you kick them off and/or remove them if needed?

Orion Platform 2015.1.0, SAM 6.2.0, QoE 2.0, IPAM 4.3, NPM 11.5, PM 2.0, Storage 5.1.0, IVIM 2.0.0

Top Replies

0 sathya4046 over 8 years ago

Could you please check your Orion server date and time? Please sync it to current date & time, if it is different.
Cancel
Vote Up 0 Vote Down

Cancel
0 scotthill over 8 years ago in reply to sathya4046

Date and time are correct.
Cancel
Vote Up 0 Vote Down

Cancel
0 scotthill over 8 years ago in reply to scotthill

Is there a way to clear the scan jobs that are qued?
Cancel
Vote Up 0 Vote Down

Cancel
0 muralikvp over 8 years ago in reply to scotthill

You may click the button cancel (Admin >> IPAM settings >> View scan job status)
Not tested but below query this will clear the job from "Scan Job Status" page.
delete FROM [dbo].[IPAM_ScanInstance] where SubnetId in (select groupid from IPAM_Group where GroupType= 8 and Address='10.199.193.0')
Place your subnet address instead of '10.199.193.0'
Cancel
Vote Up 0 Vote Down

Cancel
0 orionfan over 8 years ago

Scotthill,
Did you ever fix this? I just discovered I have many scan jobs (8 pages) that are in a queued status for over a month.
Cancel
Vote Up 0 Vote Down

Cancel
0 orionfan over 8 years ago

I have opened a case on this. I also found this in their KB: SolarWinds Knowledge Base :: IPAM Scans Not Running
Cancel
Vote Up 0 Vote Down

Cancel
0 orionfan over 8 years ago

This is what fixed the issue for me. These instructions may be unique to me because we have other Solarwinds products installed. The Jonengine.msi installation failed initially due to UAC. I had to run an elevated command prompt and then run the msi which worked.
1. Stop all SW Orion services using the Orion service manager located at start, all programs, solarwinds orion, advanced features.
2. Browse to the Path:
C:\ProgramData\Solarwinds\Installers
3. Right click on Jobengine, Jobengine.v2.msi and the CollectorInstaller.msi and uninstall each.
4. After they are all removed, run them again to reinstall those 3 files, if get a prompt, choose Typical install.
5. Restart all SW Orion services

*The User Access Control (UAC) on the Windows Server may need to be disabled and the server needs to be restarted.
Cancel
Vote Up +2 Vote Down

Cancel
0 jpashton over 8 years ago in reply to orionfan

I've been fighting this for a few months now with mixed results. I tried the fix of re-installing the Jobengine, Jobengine.v2, and the CollectorInstaller after opening a support case and getting the response to perform that. Initially, this worked, but after two days all my scans are back to queued again. This is very frustrating to say the least. Nothing seems to work for very long with this issue.
Cancel
Vote Up 0 Vote Down

Cancel
0 cbunge over 8 years ago in reply to jpashton

My scans worked until adding in DHCP servers. Bot the jobengine installers and file replacement fixes are temporary only. It's almost as if the scanning locks on one of the DHCP servers and never allows the next batch to run.
Items tried:
Adjusted number of concurrent scans - No Impact
Adjusted transient period - No Impact
Adjusted with and without SNMP - No Impact
Removed down DHCP servers - No Impact
Replaced Jobengine v1, v2, and agent files - Fixes scan for a scan or two
Reinstalled jobengines - Fixes scan for a scan or two
We don't have that many subnets monitored at this time either.
Cancel
Vote Up 0 Vote Down

Cancel
0 c4ucka54m0r3 over 8 years ago

I've just found out I am having this issue as well.
Cancel
Vote Up 0 Vote Down

Cancel