Please raise a support ticket for this, so we can track this better and provide you with more information as appropriate.
When you contact support, please provide us the following information:
- Which level EXACTLY are you on?
- Which version of the Inventory Scanner do you have? (LDISCN32.EXE)
- Whivh version of the Inventory Service do you have? (LDINV.EXE)
There's some patches that may help you (which is why we'd like to confirm what file versions you use).
We've had reports of this sort of thing beyond the fixes we've already done, which we're working on (CR # 24399) - the question is whether you're in the category of "this new stuff", or whether the previous fixes have (not yet) been applied, and thus could be of help to you.
LANDesk EMEA Technical Lead
Normally these particular errors are because the product section of the ldappl.ini is out of sync between the client and the database. The client it sending product information to the core that is not listed in the database. Usually republishing the ldappl to clients and making sure it gets down to them resolves the problem.
To prevent your service from turning off while following DaveE suggestion set your "DB Error Recovery Tries" to 10000. The default is 10. This will prevent your inventory service from turning off while working on updating the ldappl files on your clients.