FBackup Forum

As part of my backup job definition, I have it scheduled to run each night. And in the Advanced section of the job, I specify to run "Stand by" under "Run action after backup". While sometimes it does indeed put the PC into stand by, most times it does not. And when it doesn't, I see the following in the log:

[3/8/2016 12:40:17 AM] Run program/action "<Stand by>"
[3/8/2016 12:40:28 AM] Could not find running instances of bShutdownSched.exe or bShutdown.exe in order to process "saSleep" notification
[3/8/2016 12:40:28 AM] SetShutdownRights failed with error: Not all privileges or groups referenced are assigned to the caller(1300)
[3/8/2016 12:40:28 AM] SetSystemPowerState failed with error: A required privilege is not held by the client(1314)
[3/8/2016 12:40:28 AM] Warning: Could not execute action "<Stand by>". Reason: "A required privilege is not held by the client (1314)"

It seems odd that at times it works. But most times, it does not put the PC into Stand by.

Any ideas?

Hi,

Please try to see which user is logged on at the scheduled time and what are his permissions.

The user logged in is a local account, and is an Administrator.

Hi,

What is different on your computer when the problem appears?
Is the user always logged on?

As best I can tell, the job will run and put the PC (running Windows 10 btw) into standby the first time after the job has been defined. But then subsequent nights (daily job) it no longer goes into standby. A couple other observations include the fact that this defined recurring daily job does not appear in the "Scheduled" section of the Jobs dashboard once I close the FBackup app and re-open it, and only appears in "All Jobs" (although it does indicate a forthcoming job is due when I hover over the FBackup icon in the Windows system tray).

The user is indeed always logged on, however the system locks the computer after 15 minutes of inactivity. The user must login again to get back in (normal Windows security). I assume jobs that contain this user's credentials like the FBackup task does would not have an issue.

For now, I have my own standby batch file run via the Windows Task Scheduler each night an hour or so after I think the nightly backup job should complete. This .bat file simply contains the following line, and works perfectly:

C:\Windows\System32\rundll32.exe powrprof.dll,SetSuspendState

While it would be nice if FBackup could put the PC into Standby itself at the completion of jobs, I suppose this workaround works well enough.