As of a couple weeks ago just about all Windows 7 PCs will not inventory. Anyone else seen this issue?
Good morning all,
Starting a couple weeks ago, we noticed that there were many PCs in our domain that stopped inventorying. After a while we were able to narrow it down that on the desktop side, it was just about all of the Windows 7 PCs that we still run. Over 90% of them are not inventorying. We've been going through the normal troubleshooting process for this but I was wondering if this was happening to anyone else as well on the Windows 7 side.
Thanks
2 Comments
[ + ] Show comments
-
Also, I tried deleting the devices from the system. They do their initial inventory, but not the automatic ones afterwards. - wakeside917 5 years ago
-
Did anything in your network change? Or perhaps a new GPO? - JasonEgg 5 years ago
Answers (1)
Please log in to answer
Posted by:
AbhayR
5 years ago
Please refer the KAgent.log and konea.log on agent to see if you see anything erroneous. Also, check the server logs from Settings->Logs
Comments:
-
So I did run KAT on one of the W7 PCs that will not auto inventory.
Force Inventory Fails - just hangs and nothing happens
Server Retrust - Same thing here.
I Kapture the logs but I'm not sure what to look for. Can anyone advise?
Thanks - wakeside917 5 years ago-
at this point, I would contact support - JasonEgg 5 years ago
-
Also in the konea.log I see the following errors. Do these mean anything to anyone:
|ERROR|process.go:143:func1 | Module Exited |{"err":"exit status 1","module":"clientidentifier"}
|ERROR|requesterlistener.go:68:Run | Stop Requester Listener |{"err":"accept tcp 127.0.0.1:51519: use of closed network connection"}
|ERROR|exechandler.go:86:func1 | Error killing |{"err":"exit status 1"}
|ERROR|sdk.go:45:func1 | konea not running, exiting|{"current ppid":2156,"initial ppid":2156} - wakeside917 5 years ago
