Follow the instructions here Database Repair Utility (DBRepair.exe download) Unfortunately there is no real way of finding out which client corrupted the metadata, however, there may be something in the works for this.
1 of 1 people found this helpful
The most common cause is "old clients" - keeping one's clients up to date does a good job of keeping it to a minimum.
But yeah - you will want to follow the DBREPAIR process (make sure you have a DB backup, just in case). The most important thing to remember is to STOP the Inventory service before running the tool. Otherwise, the cached DB corruption will be written back (in the best case) or worse - you break your DB well and proper.
LANDesk EMEA Technical Lead.
Thanks zman & phoffman, that's worked perfectly.