Scheduled profile doesn't run or log error(canceled by user)

[bartsides]

Hello Gents,

We've created and distributed profiles that work well on many computers except one.

OS: Windows 7 x64
SyncBackSE Version: 6.0.3.3


The profiles are scheduled by a single profile group to run every day. They run just fine if run manually but when run via schedule it says the following:

The operation was canceled by the user (0x800704C7)


I ran into this issue before and the solution was to group the profiles as scheduling too many at the same time caused issues. I checked in the Task Scheduler and the computer only has one scheduled profile. It said the following in the error logs:

Task Scheduler failed to launch "...\SyncBackSE.exe" in instance "{...}" of task "...\Backup Profiles". Additional Data: Error Value: 2147943623

I'm not sure if that error means anything of importance. Any help or guidance would be much appreciated.



Thanks,
Bart

[Dave Wilkins]

Um, that's the same error expressed in two different bases (2147943623 is the decimal version of the hex value 0x800704C7)...

But that's not a value returned by SE (see Help > Search > 'command-line' > top hit > scroll to bottom for the values we return)

I suspect that is an error from the Task Scheduler itself. Unfortunately, I can find no reference to either of those numbers in our KB, ticket system or forum - and a Google for either doesn't get very far (especially if you add the term 'schedule/r') although this hit might be food for thought (changed any passwords recently?)

Can you schedule anything else (e.g. Notepad)? Note that you'd probably need to set the Task to 'run only when logged in' (and be so) or the Notepad instance will open in session-0 meaning you can't see (or close) it.

While on the subject of session-0, run Task Manager, switch to Processes tab, set it to Show Processes From All Users, and count the number of SyncBackSE.exe instances listed. It may be that an instance is already running (maybe stuck...) with that same command-line (group name argument) - if so, SE will reject the new (identical) command-line. There are options in the Task what to do if an instance is already running which may be useful

Have you tried individually scheduling a single profile and testing what happens? The return codes in SE for a group are very limited (given that different member profiles might have different results - cannot report them all in one string...), so you might get different/more useful return values with a single profile (if it's getting as far as starting SE)

(Incidentally, you should update to the latest SE version: 6.0.3.3 is out of date)

[bartsides]

Thanks for the speedy reply! I will run some tests and see what happens.


Thanks,
Bart

[bartsides]

Sorry for the delay. I upgraded our user's SyncBack to the latest version (6.0.12.0) a while ago. Just found out that the profiles only run when the user is there to key in his Window's password. Any idea on why that would happen? It seems like his username and password didn't save correctly to the profile/scheduled task. Tomorrow I am going to reinstall SyncBack and import the profiles again to hopefully start from scratch.

Thanks,
Bart

[Dave Wilkins]

I'm not clear what you mean by '...profiles only run when the user is there to key in ..'. How does he know to do so? Is there a prompt? Or do you mean they only run if he is already logged in (beforehand)? If so, check that you do not have 'Run only when logged on' checked (in the Task)?

Note: I did mention this previously (with regard to a test Schedule for NotePad, otherwise you wouldn't be able to see if it worked). The same applies for SE - you won't see it unless that option is checked, but SE will close itself on completion of the profile/s (unlike Notepad), and generally you do want it to run while user is not logged in - so you usually shouldn't use that setting, unless user is non-admin, in which case, yes, he'd need to be there/logged in.