This could be the issue with the communicating the LANDesk Core serve. For patch definition the client machines access this http://coreservername/wsvulnerabilitycore/vulcore.asmx link. So try accessing this link from the client machine where you get this error. If it fails try with IP address of core server instead of Serve name. If succeeds with IP address then it's clearly a DNS issue.
If changing the IP address solves the issue the there are 2 soluions for it..
1. Try installing agent on those machines with IP address instead of Server name in the agent configuration.
2. Add an entry in the hosts file located the C:\Windows\System32\drivers\etc folder of those machnes having this error. (you can achieve this using a custom file transfer script to all machines at a single click)
Hope this helps...
Is there new information on this issue or has the DOC-2544 disappeared for another reason?
I would like to know as well, we have some issues in LDMS 9 when distrubiting packages and getting the same error message.
We are also receiving this error on all stations since I have upgraded to 9.0, any suggestions?
Anyone find a solution for this?
Go to HKLM\Software\Intel\LANDesk\Common API and delete the UniqueID
(For 64 bit OS HKLM\Software\wow64\Intel\LANDesk\Common API)
Run an inventory scan from the device.
Problem should be resolved.
how do you accomplish that on 30+ machines?
Use a custom script with REMEXEC commands and send that out to those 30 computers.
..and how pray tell is that to work when "Nodes reported device id is not in the database" causes jobs to fail?
Custom scripts are much more robust so there is quite a big chance it will work.
1 of 1 people found this helpful
I found another thread here which mentioned restarting the DB instance and then restarting core server.
After restarting my SQL server and the core, it seems to have resolved itself. Of course it could be a coincidence, but....
This is what fixed it for me and this is from my notes:
Sometimes landesk clients report the error message "Node's reported ID is not in the database" when attempting to run scan and repair tasks.
Run the following command on each client affected (change the ip address to the core server IP address that the client points to)
"C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /NTT=192.168.1.10:5007 /S=192.168.1.10 /I=HTTP://192.168.1.10/ldlogon/ldappl3.ldz /NOUI /NOCD /F /SYNC