bme wrote:This all worked fine on XP with SyncBackPro.
The Windows Task Schedulers Pre-Vista (WinXP, etc) and Vista-or-later are two radically different versions. Note that there is no scheduler in SE/Pro itself - we use a drill-down to the Windows Task Scheduler service
http://support.2brightsparks.com/knowledgebase/articles/211489-the-windows-task-scheduler
Successful profile runs under the Scheduler of WinXP doesn't mean schedules in Win7 will be successful as well (it could certainly fail if you did not set it up properly).
bme wrote:From SyncBackPro Schedule window....
Here is an error code of a scheduled profile that did not run:
The profile run failed (0xFFFFFF95)
The first error 0xFFFFFF95 is from SyncBackPro (Pro is reporting status of the profile run back to the Scheduler, i.e 0xFFFFFF95 is a Pro result code). You can open your program contextual Help and use the Search tab to search for this error. This error is just telling us that the profile run has failed. As to why it failed, there is a wide variety of reasons (can't find/locate path/media, Access Denied on a single file, etc).
In addition, please note that if SyncBackPro reported back that return code (which is an error), then the scheduled profile must have at least tried to start/run, or else that code wouldn't have been reported back. What probably happened was that the program have been triggered, it then found the profile, and then something caused it to fail and the error was reported. We will then have to check what the actual failure was in SyncBackPro.
bme wrote:This one said it was but did not:
An instance of this task is already running (0x8004131F)
The second error 0x8004131F is an error code from Windows. Windows report it to us, and we quote it back to the user. This error means that Task Scheduler, while trying to run an instance of the scheduled task, has found another instance of the same task is already running.
And based on the (default) settings in Task Scheduler, it will not start a new instance when it finds another instance of the same task is already running, hence the reason you are getting this error. And when Windows say it detects another instance running, it is usually correct (unless your Task Scheduler is somehow broken), and we can't argue with it.
You could try to restart your Windows 7 system to clear any residual memory and try again.