Could you please post the last SQL command, as logged by Profiler, when you run the backup via the sys_Backup procedure?
Best guess would be that the SETUSER function is raising that error. What happens if you run the
when logged on using the same account that the SQL Backup Agent service uses?
Best guess would be that the SETUSER function is raising that error. What happens if you run the
| Code: |
| SETUSER 'fditbackup' |
when logged on using the same account that the SQL Backup Agent service uses?