Still cant get task to run
Hi All
i am using TI2011 build 6942, i have been having problems getting a certain backup task to run, i recently posted a question asking how to zap a task schedule, i successfully deleted the task from the scheduler, i then deleted the task from within TI and started from scratch.
But today the task didn't run again!, i have noticed in the attached log that it mentions something about the scheduler failed to run because of error 1327 (logon failure) i have no idea what this means.
What i cant understand also is that all other 7 backup tasks run on time as they should without any problems, please can anyone help??
Thanks as always
Pete
| Anhang | Größe |
|---|---|
| bc5365f6-29f5-4ec8-89a3-5cfc0394ab25.txt | 3.75 KB |
| acronis_2.png | 31.8 KB |
- Anmelden, um Kommentare verfassen zu können
Be sure that drive X contains a file with the word "Vertbatim" on one line (no quotationss)
X:\drvnotify.txt
Verbatim
Also note that drive X must be recognized by Windows before it can be recognized by Drive Notify. Are you sure this is happening.
Your log attachment shows an error message but not the complete text of the error message. Please clarify.
If you are editing an existing task, the results are not always predictable.
You could use the Windows Task Scheduler and have it wake the computer just prior to 1 by opening Notepad, or some other meaningliess task.
- Anmelden, um Kommentare verfassen zu können
Hi GroverH
The drive x has got all the info in the root folder, like I said in my post I have quite a few other tasks and they all perform perfectly, thats what I can't understand.
Also I am not editing an existing task,I have deleted the entire task and started from scratch.
Not quite sure what you mean by the log attachments, I thought I had copied everything that was there?
Pete
- Anmelden, um Kommentare verfassen zu können
Yes, I found the text. It was not being truncated. Here is the error message. Now we have to find which part of the error message is applicable.
message="Scheduler failed to run task "D-Drive" with GUID 'BC5365F6-29F5-4EC8-89A3-5CFC0394AB25' because of error 1327 (Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced).
I am not sure as to which part is related to this issue. All I can do is to offer some suggestions to try.
What time was this error message created? Was it at backup time? If it was later, try temporarily using Windows Task Scheduler to wake up the system just prior to 1. In order for DriveNotify to work, it must be memory resident prior to TI starting. If needed, use Windows Task scheduler to start Drive Notify.exe just prior to 1 am.
Does Drv Notify have the proper permissions? Try right clicking on the exe file and give it more permissions.
- Anmelden, um Kommentare verfassen zu können
Hi
Well after i sent my post i decided to try yet again, i completely removed the task from TI, i made sure the Script was deleted then set the backup task up again, i set it to back up at 7.30pm tonight and it worked perfectly.
I am now waiting with baited breath as it only performs the back up once a week so im afraid my next post might be a while :-)
Thanks
Pete
- Anmelden, um Kommentare verfassen zu können
I was adding things to my post which you may not have seen. Keep me posted.
- Anmelden, um Kommentare verfassen zu können
Thanks, i will keep you updated of course, just keeping everything crossed that its now working correctly :-)
Pete
- Anmelden, um Kommentare verfassen zu können
you can use the "backup now" option which will tell you whether the backup function will work. It won't tell you about the schedule but it will identify if the process will work. Be sure that Drive notify is memory resident before you run the backup.
- Anmelden, um Kommentare verfassen zu können
Thanks GroverH, i can confirm that the backup now option works ok, like i said i will keep you posted on what happens next.
Pete
- Anmelden, um Kommentare verfassen zu können
Hi GroverH
Well its been a week and the backup was supposed to happen this morning but it didn't, but this time i got no error message when i turned on the pc, instead the backup just started as it was set to start if the task was missed.
i just really cant understand why the scheduler isn't working on this one task, like i said before i have 7 other tasks and they all run perfectly so im reluctant to try a reinstall of TI.
Its baffling, i completely removed the last task, as well as all the backup files & folders, also made sure the script was removed so there was no conflict.
I just have no idea what to try next, as like i said im not even getting an error in the log file :-(
Pete
- Anmelden, um Kommentare verfassen zu können
My next step would be to use the Windows Scheduler to start this specific task rather than TrueImage. Click on my signature index below and look at item #3-H which explains how.
Or, another test could be to use Windows Scheduler to wake the system just prior to task wake up time as I suggested in post
#2 above.
Do you have the computer sleeping or hibernating or completely shutdown at time the task is supposed to run?
- Anmelden, um Kommentare verfassen zu können
Ok Grover
This is crazy, i changed the task to run on Friday morning not on a Thursday morning and blow me down the bloody thing ran this morning!!
i don't know if its conflicting with something else that's running on thursday, but its not another TI task so who knows. This problem gets stranger & stranger each time!!
Will keep you updated as usual & thanks for all your suggestions & advice.
Pete
- Anmelden, um Kommentare verfassen zu können
Compare the system status just prior to both the Thursday or Friday backup times. Did other programs keep it from going to sleep
- Anmelden, um Kommentare verfassen zu können
GroverH wrote:Compare the system status just prior to both the Thursday or Friday backup times. Did other programs keep it from going to sleep
Hi
sorry you have lost me on this, how do i do it?
Pete
- Anmelden, um Kommentare verfassen zu können
Yes, easier said that done. What I was thinking was to review the Windows Task Scheduler and see what tasks might be scheduled on Friday and Thursday, etc. Maybe there is some type scan going on. I am only clutching at straws trying to find differences. Do try to setup Windows Task Scheduler to wake the system just prior to Friday backup just to see that provides a temporary solution.
A review of Windows Events at the Thursday and Friday time period may also be of assistance.
- Anmelden, um Kommentare verfassen zu können
LOL, i couldn't see anything that would interfere with the task, i have now set the windows scheduler to wake the pc so ill keep you updated on how it goes.
Thanks as always
Pete
- Anmelden, um Kommentare verfassen zu können
Hi GroverH
Bad news i'm afraid, 2 tasks were set to run last night, D Drive back up at 2am & email backup at 5am, the email backup went fine but the d drive back up failed again with the same error message! Windows Task scheduler was set to wake the pc 5 mins before both tasks started.
i have attached a screen shot, can you suggest anything else to try :-(
Pete
| Anhang | Größe |
|---|---|
| 100680-101236.png | 34.74 KB |
- Anmelden, um Kommentare verfassen zu können
Is it worth trying a repair install?, if so how do i go about it?
But will this cause more harm than good as all the other tasks work fine & even this D Drive task works when i use the "Backup now button"
Pete
- Anmelden, um Kommentare verfassen zu können
Doing a repair is certainly an option. Do you have your install set for "all users" or a "single user"?
A repair should not cause you any issues but you have (or will make) a current backup so any issues could be corrected by the recovery of a current backup.
To do the repair.
Restart the downloaded installation file for the version/build you are using.
Choose the install option.
This screen will change and offer you a repair or modify option. You can choose either but choose the repair.
The install will overlap the existing install.
If you keep the Windows Scheduler,edit the start time from 5 before to 1 before so it has no chance to go back to sleep.
According to the error message, this looks like a security or privileges issue.
Maybe someone else can offer a fix.
- Anmelden, um Kommentare verfassen zu können
Thanks GroverH for your help & Advice, im just very reluctant to try the repair option as it just doesnt make sense that all other 6 tasks work fine, i understand what you are saying about making sure you have backed up & it "should not cause any problems" but im sure somehting else will go wrong!! :-)
I do agree with you that it must be something to do with privileges, the only thing that is common in all this is that this backup task is the only one that includes the D drive, all other backup tasks are performed on the C drive, im going to have another play over the weekend.
Just one question, i have looked at you pdf on using the windows scheduler to run the task, if i copy the script does this also run the pre & post commands that are set up within that task?
Pete
- Anmelden, um Kommentare verfassen zu können
We have covered a lot of area in this posting. Would you confirm
1. which version/build of TrueImage is involved in this task
2. whether Drive Notify is involved.
If Drive notify is part of the pre/post,
edit the prepost and look the the work directory instructions. In txt posting above, the ending slash appears wrong on the work directory.
- Anmelden, um Kommentare verfassen zu können
Hi
i am using TI2011 build 6942, Drive Notify is invloved but that seems to be working perfectly ok.
Pete
- Anmelden, um Kommentare verfassen zu können
If Drive notify is part of the pre/post,
edit the prepost and look the the work directory instructions. In txt posting above, the ending slash appears wrong on the work directory. Ending slash not needed.
In order for the pre/post to succeed with the Drivenotify,
the Drive notify kernel must already be memory resident for the pre/post drive notify to work. This memory resident item is often put there by a startup command.
- Anmelden, um Kommentare verfassen zu können
Hi Grover
Drivenotify is part of the Pre- Command, i will wait until i get home this evening and i will post how its set up, but i have already checked it once to make sure it was set up the same as all the other tasks, they also back up to the X drive.
Also when i use the Backup Now button seems to work on that part as well, i had Mudcrab send me a file so it would do what i wanted it to do.
Trueimage is set to wake the pc, then drivenotify looks for the X Drive if its there then the backup starts and then when finished the pc is put back to sleep, if drivenotify cant see the drive it then cancels the backup and the pc goes back to sleep. Like ive said before its been working great for months & months so somewhere down the line something has changed thats stopping this one task from working. Grrrrrrrrrrr
Pete
- Anmelden, um Kommentare verfassen zu können
another option would be to relocate the commands from the prepost into a batch file (prefer a cmd file) and then have the prepost run the cmd file.
I prefer the having prepost run execute a file rather than execute individual commands.
The contents of the command file would be
C:\DrvNotify\DrvNotify.exe /wait:exit Verbatim
Save file as
C:\DrvNotify\Verbatim.cmd
Into the prepost, remove the other and put this into prepost
C:\DrvNotify\Verbatim.cmd
-------------------------------------
As the error message was generated so the task attempted to run, this does not appear to be a scheduling issue but more how the prepost commands are handled or authorized. This is one reason my suggesting prepost run a cmd file. Who know but I may be "totally wrong."
- Anmelden, um Kommentare verfassen zu können