Thanks for your reply. I did check all my jobs and job histories to make sure they are working correctly.

What puzzles me is that, as indicated in the KB article, this is a problem for SQL 2000 and 7.0, and was corrected by sp1 for SQL 2000 and sp4 for SQL 7.0. So I assume it's not an issue for SQL 2005 anymore and wonder why I got it.