New week new troubles: SnapManager SQL created some backup jobs within the SQL Server 2005 - the job itself could not be run/executed.
The owner (...) of job <Job Name> does not have server access.
This strange behaviour i got only with SQL Server 2005. With SQL Server 2008 i could not reproduce it. The user who created the job and was the owner of the job had SQL sysadmin role assigned. I found some hints to this behaviour: a restart of the SQL Server Agent should work. In my case i didn't work that easy.
If i change the owner of the job to the builtin user sa the job is able to run...
It would be nice to understand the issue....
No comments:
Post a Comment