Coincidently this very thing happened to me last week and I finally got it resolved. I was changing the SQL Services to run under a domain service account from localService...