I had this problem and finally got thru it by adding the domain account used to start SQL Server and SQL Server Agent to the local administrators group, as well...