I've been pretty busy trying to track down this bug (I've seen the same thing happening to us over at DNA@Home), and tried a couple changes to the database today. Is anyone still seeing this issue, or did that happen to fix it?

More...