Could you attach the ldappl3.ini? It resides in \\core\ldlogon folder
it could be that your database has corrupt entries which "blocks" the correct one for query creation.
Try to check and repair the Custom Data entries with DBREPAIR:Database Repair Utility
the database repair solved our problem.
Please make sure you've done a COREDBUTIL -> BUILD COMPONENTS after running DBREPAIR (and please make sure your Inventory Service is stopped during this - can't stress this enough) - so that all the data is correctly linked together again.
LANDesk EMEA Technical Lead
it would be nice to have a automatic task to do this...deactivate inventory service, cleanup with dbrepair, start coredbutil, activate inventory service.
But I fear I need a external tool for this... (like DatabaseDoctor...)
We've to do this every week for all cores and the roll-up. Some cores are cleaned in some seconds, some need half an hour (the roll-up cleaning need much more time). It's a strange task and I can't find the clients which are involved...
You could automate the process via scripting, but we don't do that for the simple reason that DBRepair cleans out the Unmodeled data from your DB - this includes Custom Data that's being collected via the ldappl file, etc. Dbrepair is considered a 'use only when needed' tool.