I have had the same problem described above and I went ahead and ran it manually as the user that the SQL Server Agent runs under and selected 'y' on...