-
1. Re: newly deployed agent won't scan inventory Return code 2
Use /V on the client. What message does the scanner give you on the client?
Mark McGinn
MarXtar Ltd
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements
- Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing
- State Notifier - Real-Time Device & User State Inventory Updating & Alerting
Update - WoW & State Notifier now integrate for even more functionality
-
2. Re: newly deployed agent won't scan inventory Return code 2
using the /v switch displays the normal window
It finishes the Hardware and Device scan, then goes through the software scan.
-
3. Re: newly deployed agent won't scan inventory Return code 2
More specifically, here is the entire command
"C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /NTT=ESPADA:5007 /S=ESPADA /I=HTTP://ESPADA/ldlogon/ldappl3.ldz /V /F /SYNC
with Espada being my core server
-
4. Re: newly deployed agent won't scan inventory Return code 2
If this completes without error, then the client believes it is scanning successfully.
Are you getting any error scans on your core server? Are scan files building up in LDSCAN? Any event log entries? Have you tried restarting your inventory service or core server?
Mark McGinn
MarXtar Ltd
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements
- Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing
- State Notifier - Real-Time Device & User State Inventory Updating & Alerting
Update - WoW & State Notifier now integrate for even more functionality
-
5. Re: newly deployed agent won't scan inventory Return code 2
No error scans on core
Scan files aren't building up in LDSCAN
Which log should I look in specifically.
Tried restarting the inventory service on our core and then rescanned with same result.
The only other thing to note is that we are close to our license limit (with in 1-2) and have contacted our vendor for more licenses. Could this affect the inventory ability?
-
6. Re: newly deployed agent won't scan inventory Return code 2
Eventlog on the core server.
This sounds like a duplicate device ID issue. Run the scanner again, but this time use /O= and output this to a file e.g. scan.scn.
Now try copying this file to the ldscan directory. Does it disappear? Does the machine appear in the database? If not, then open the scan file in notepad and just change a couple of the characters in the device ID and then copy in again. Does the machine appear now?
Licensing shouldn't affect this, if it was really bad you wouldn't be allowed to log into the console.
If the editing works, then see if you have duplicate device ID detection enabled?
Mark McGinn
MarXtar Ltd
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements
- Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing
- State Notifier - Real-Time Device & User State Inventory Updating & Alerting
Update - WoW & State Notifier now integrate for even more functionality
-
7. Re: newly deployed agent won't scan inventory Return code 2
Putting it up on the core under ldscan moved it to ldscan\ErrorScan first time after it "disappeared"
Renamed the Device ID, sends it to ldscan\ErrorScan
Get the following errors in Event Log:
Event ID 4110: The size of the Computer Description is too small. Increase its size by at least 133
Event ID 4100: Database exception: Scan.scn, LDInv.dll - 2147217887
Multiple-step operation generated error. Check each status value.
Update Table:Computer Column: DESCRIPTION PK:' Thread ID: 7564
-
8. Re: newly deployed agent won't scan inventory Return code 2
Thank you for sending me to the event logs.
I added a Computer Description to the PC in system properties and it now scans and picks up fine.
Funny thing is none of the other computers on our domain have a Computer Description.
