Aparently in this case restarting the MSSQLSERVER service which restarted the SQLSERVERAGENT service fixed the problem.<BR><BR>It looks like the problem was that when the server was rebuilt 3 weeks ...