Syncovery Support Forum

thanks for the clarification. I will turn off shadow copying.

I'm running about 10 profiles at about the same time and various of them get stuck on 'Running (Shadow (Xs))' - see screenshot.

If I cancel the job it runs next time without a problem (but another may stop with the same message).

thanks

Hi

I am experiencing a problem with the display of the 'Next Run'.

Please see screenshot from today showing the next runs as in the past 2023-04-19.

If I swap over to the Scheduler tab and back to the Profile tab then the display shoes the correct time for next run.

Hi

I'm experiencing the same problem with version 10.4.0.

Is there any progress on fixing this?

I think there is a bug - see screenshot showing web page results referring to second last run rather than the most recent.

Thank you for all your suggestions They really helped.

I was able to get this to work by adding an undocumented command line parameter "-accepteula" to the psShutdown command. I found the parameter online via Google when I searched for "how to remotely sleep computer".

When I run the profile Attended the cmd file executes ok - log says "Running as : Tornado\Peter (not Admin)" When the profile is run by the scheduler service the cmd file timesout - log says "Running as : Tornado\Administrator (Admin)" I can successfully run the cmd file outside of Syncovery - both ...

I'm still having problems running a simple job after the profile runs.

I've got a simple cmd file that's only got the command "pause" in it and it won't run in the background. It will run if I do an Attended run.

Any ideas?

Yes, Wombat is another PC on the local network.

I'm trying to suspend/sleep the computer called Wombat. Any suggestions?