Background Scheduler won't stay running in Win 7

[RadicalDad]

The background scheduler keeps quitting in Windows 7 Pro. We have 3 brand new machines (Lenovo laptops), two of which work fine. I have just configured the third laptop today and the scheduler won't stay running on that machine. The three machines are fairly similar (though not identical). I haven't seen any large differences while configuring them, so I can't imagine what the problem with the third machine might be. Help appreciated.

Thanks,
Bruce Morris

[superflexible]

Do you mean it stops during a Windows session, or doesn't start when the user logs on?

[superflexible]

If the scheduler doesn't start when you log in, it will help to install it as a service. Please see

http://www.superflexible.com/docup.htm

[RadicalDad]

Just to put closure on this, the problem went away on its own. I have no idea what the problem was.

For lurkers who might be having a similar problem: On the initial sync I had a problem where the scheduler was shutting down, but that problem had already been solved. FYI, here is what happened. Using the old Win XP machine, I copied My Documents to the NAS. Then using the new Windows 7 machine, I copied the files from the NAS to the new machine. Windows 7 wants to clean things up along the way, putting My Pictures and My Music into the new Win 7 folder structure. One folder had a bunch of .eml (email) files, and I'm guessing Win 7 did something strange with these. After several attempts at a sync where the schedule kept shutting down, I did a manual sync on each profile until I was able to track the problem to these faulty .eml files. I deleted them all on the Win 7 side and let SFFS do the copy, and then all was happy.

After the above, I was still getting random shutdowns of the scheduler but could not trace it to any one profile or file copy. At that point I started this thread. But the problem stopped happening after a few days without any intervention from me, so all is good.

[superflexible]

The new version 5.54a now fixes an issue that could have prevented the Background Scheduler from launching after user log-on on some systems.