I did a search of the forums and found only a few references to this problem. The solution (for 2009 and above) seems to be to do an extended database repair in Content Manager. Depending on the quantity of your installed assets this can take some time.