PRE command won't work on new computer at start up but works fine when submitted manually
I am doing a weekly Image backup on my wife's computer. This computer is quite new with SATA3 and SSD for main drive.
The ATI2014 backup starts at boot up but fails with error code 1 due to the Pre-command. I then submit the backup manually and it always works. The Pre-command just runs Microsoft Security essensials for a quick scan before starting the backup.
I thought adding a 3 minute delay would help, but doesn't make a difference.
My personal computer is SATA2 with SSD and I have no problem running the same type of PRe-command on my computer at boot up
Grover has suggested C2G for pre/post commands which is an option but I would like some feedback first before undertaking switching her machine to use C2G which seems like a major change.
My personal experience is that any pre or post command needs to be in a .cmd file. For some reason a .bat file never worked for me on WIN 7.
My Pre-command is in a .bat file. I have tried .cmd files with some success, but usually .bat and .cmd work OK for me.
As I said, works fine when the Image job is submitted manually, but for some reason the scheduler can't execute the same Image Job because it always kicks out on execution of the Pre-command. AND the same Image job on my other I7 computer with SSD drive and SATA2 works fine with the scheduler. the only time I have an issue is with the newer I5 computer with SATA3 and SSD drive. I thought it might be a timing thing since this job is kicked off at boot up time and thus I added a 3 minute delay, but this didn't help either
Within Windows Explorer, RIGHT click on the bat file and click on propertiess.
Look under security and edit security and make sure all users listed have full control to do everything.
You could also achieve the same thing by opening NotePad in the Run as Administrator mode.
and open and save the bat file while notepad is in the elevated security mode.
GroverH . I had to wait for Scheduler to run, Weekly job ran today and it seems to have worked with Permissions changed - thank-you
Glad it worked for you. There is usually a reason. We just have find the right reason and sometimes that is trial and error.
Any change to your bat file should be done when Notepad is in its "Run as Administrator" mode.
I have this same Bat file set up to run as PRE-command in Acronis schema on 2 different computers. The original permissions were identical on both my I7 and my I5 computers, yet I had this issue on the I5 computer. Your suggestion has fixed it. I suspect there is a problem with Windows.account in my I5 computer schema but not worth worrying about any more.