I have a simple procedure that backups a database, and that works fine when executed directly.

However, when called from a scheduled job, it fails because it's not being allowed to rename the backup .tmp file to the file with the .EDBBkp extension and so it continues to try every minute, each time creating these large .tmp files that are really the backup file:  

File Manager error (Cannot rename the file xxxxxxxx.tmp to xxxxxxxxxxx.EDBkp...)

Originally I tried this putting the SQL directly in the JOB, but had the same problem.  (Again, the JOB would work if I chose to run it as a script.)

This is on Windows Server 2012 with the everything running under Administrator.  

Any ideas on why something would be okay for the OS as a procedure, but not when called from a job?

Alan


If you're running the server as a service try running it as an application.

If that works then its a permissions problem - services don't run in the same user space as an application (or so I believe). I always ran the server as an application so I'm not certain.



Roy Lambert

Thanks, but I am running as an application.



Roy Lambert wrote:

Alan


If you're running the server as a service try running it as an application.

If that works then its a permissions problem - services don't run in the same user space as an application (or so I believe). I always ran the server as an application so I'm not certain.



Roy Lambert

Alan,

In addition to what Roy said about OS permissions, there is also the execution context of the jobs in EDB, that is by default under the user "System", however you might be executing this job using another user. Can you check that out?

--
Fernando Dias
[Team Elevate]

I did create the job with RUN AS "System"  and that is the User if I look at the job with Alter Job in EDB Manager.   

BUT...I found the problem.  I don't know why I didn't think of this, but this particular store (and I have lots of them) is in a DropBox folder.  Disabling DropBox allows the job to run successfully every time.

Unfortunate, because I like to do backups to DropBox to get automatic off-server backups.  

I still don't know why doing it as a procedure is fine, but not as a job....but it is definitely DropBox.

I'll move the backup store somewhere else and periodically copy those files to DropBox some other way.



Fernando Dias wrote:

Alan,

In addition to what Roy said about OS permissions, there is also the execution context of the jobs in EDB, that is by default under the user "System", however you might be executing this job using another user. Can you check that out?

--
Fernando Dias
[Team Elevate]