I have found 3 separate postings reporting this bug for different versions of SQL Server, from 2005 to 2012. The answers to these posting suggest the the fix has already been put in with SQL Server 2008 Service Pack 2. We are currently using 2008 woth Service Pack 2 but we still have this problem. We have two separate jobs that are supposed to run on a specified date once a year. But both have been run on the same day of the following months. One of the jobs is to insert data for the new year and has caused and will continue to cause havoc if we allow the problem to continue because of the incorrect date when the job was run.
The version we are currently using is: Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)