Are you seeing this error when kicking off an inventory scan from the core or directly from the machine? Are you seeing this on multiple machines or just this one? Please let me know.
This error turn up when start inventory scan from the core or according to the schedule configured in the agent inventory.
So LDAPWHOAMI doesn't do a lot of complicated stuff - it tries to resolve "who is the user in AD" (i.e. - what groups does he belong to) and tries to do the same for the machine it's on.
You can run LDAPWHOAMI "standalone" (and it'll give you the output it finds) - so you can check if it'll crash if you "just' run it (I've never seen it crash to date myself). Since it interacts with AD, you may benefit from having something like PROCMON running, to see if there's anything obvious around its crashing and - if there isn't - then providing the PROCMON trace to our support would be helpful as a starting point.
The exe doesn't really do anything complicated, so somewhat surprised to see it crash. Is that just on "one box" or is that happening consistently across your estate?
We found the problem: distinguishedName (user account parameter from active directory) It has too many characters, in our case 285. In ldms9.6sp2 the problem was not.
Ah cool - good to hear that this you got unstuck then .
You can request the latest service update for LD 2016 from LANDesk Support (SU3 at the moment - SU4 should be out in a few weeks), that will probably include updates for the same binary in 2016 I'd expect.
If NOT, then just open this as a regular support ticket & this should be a fairly quick affair, since you've tracked down where the problem is already.
We found the problem but does not fix it because we can not change the length OU in AD. For us it is not a solution. Tell me please where to download SU3.