Before posting, and to avoid disappointment, please read the following:

  • This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
  • If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.

User aborted (FFFFFF98)

SyncBackFree is the freeware version of SyncBack. It is *not* an evaluation version of SyncBackPro/SE.
Post Reply
Lindsay Graham
Newbie
Newbie
Posts: 4
Joined: Mon Aug 19, 2013 1:57 pm

User aborted (FFFFFF98)

Post by Lindsay Graham »

SyncBackFree 9.1.12.0 (running under Windows 10) is scheduled on 2 computers to run daily. Computer A -- no problems. Computer B -- scheduled run fails with error code as above.

2BrightSparks Support said "... FFFFFF98 is an error code from your Task Scheduler, which indicate an abnormal termination of your profile run. It could be due to mis-configurations in your profile settings or maybe the profile needs user input to continue the execution. Can you try running the profile manually (Ctrl + R) and see if it runs successfully?"

Running manually (Ctrl+R or Ctrl+W) is fine, no problems. Cannot see any mis-configuration or user input requirement. I've several times deleted the schedule and re-input it, but still the error occurs. Any ideas or suggestions?
Lindsay Graham
Newbie
Newbie
Posts: 4
Joined: Mon Aug 19, 2013 1:57 pm

Re: User aborted (FFFFFF98)

Post by Lindsay Graham »

No replies on this topic, so I don't know whether it's not been read or nobody else has had the same problem.

But, for the record, it seems to have been fixed by simply deleting the scheduled group and all its profiles, and then recreating the whole thing. Now it works OK!!
Post Reply