And did you perform changes to scheduler using terminal services or standard desktop? This could occur when using not fixed version on TS - if this is the case so it is just same bug as you have reported some time ago.