Same thing started happening to us this morning.Ran the setup /force (and reboot) and the problem still exists.