Error from task scheduler

[numknuf]

When using the task scheduler to run synctoy 2.0 (SyncToyCmd) I get this
error message:

SyncToyCmd has detected that the folder pair User Backup has not been
synchronized yet. Please run SyncToy.exe to complete the initial
synchronization.

If I run the same program from the command line it runs fine.

(Ps: The help file says all logs are written to the event viewer, but they
are not...)

 

[numknuf]

It seems the SyncToyCmd does not run correctly if the task is set up as :

x Run whether user is logged on or not

This works fine:
Run only when user is logged on

 

[Joe]

Are you sure of this? I had this setting but still get the same error.

 

[Ashish]

Did you try running the folder pair atleast once using the UI as the error
message states? The command line issue should resolve after that. Let us know
if it doesn't.

Ashish Shah
SyncToy Development.

 

[mvgroup]

I tried running via the UI and I still have the same issue. I t won't run
unless logged on.

 

[Sirbishop]

Was this ever addressed? I am getting the same errors on every Vista machine
I run SyncToyCmd on.

And YES I have manually ran it first.

I get this message from the cmd prompt as well as when I have it scheduled
as a task.

 

[Swifty]

Was this ever addressed? I am getting the same errors on every Vista machine
I run SyncToyCmd on.

And YES I have manually ran it first.

I've lost the beginning of this thread, so please excuse me if I'm way
off. I think my problem was the same. Then I opened Synctoy.exe and for
each pair, did a *preview* and from the preview did *run*. This cleared
up my problem. I hope yours is the same.

 

[Daniel Cates]

I have the same error. When the scheduled task runs, the first of two folder
pairs runs, the second says that it needs to be synchronized first.

I have already synchronized it manually with synctoy.exe. The sync works
fine through the UI with synctoy.exe.

This error occurs whether I have "run only if logged in" checked or not. I
have tried deleting and recreating the schedule to no effect. I have tried
running just the folder pair in question on it's own schedule. This gives
the same error. The same error is also reproduced when run manually from the
command line.

Any new advice is appreciated.

Daniel Cates