Hi,

I can concur regarding this being caused by the SQLAgent service account being configured with a domain account. Impersonation may well solve this but to work around the issue for...