A review of the logs show the my two scheduled profiles ran successfully however the field "Last Successful Run" does not update with the correct time stamp. A time stamp of a prior manual run is shown. Can anyone offer a fix?
Thanks,
Kevin
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.
- If you are entitled to technical support then please submit a support ticket. Please do not post the same question to the forum and also via a support ticket. Once again, 2BrightSparks does not provide technical support via this forum.
No time stamp update to "Last Successfull Run"
-
mcneillkj
- Newbie
- Posts: 2
- Joined: Sat Sep 30, 2017 2:43 pm
-
cliffhanger
- Expert
- Posts: 606
- Joined: Tue May 31, 2011 5:59 pm
Re: No time stamp update to "Last Successfull Run"
Did you try pressing F5 to refresh the main window contents? (More background here (ignore last two posts in thread, which are a different issue)
If this does not solve it, I would suggest making a Support Zip with debug-out of one of your profiles (generate the Zip after it runs on schedule in debug-out mode / if the LSR stamp still does not update) and sending it to 2BS Support (details in KB article)
If this does not solve it, I would suggest making a Support Zip with debug-out of one of your profiles (generate the Zip after it runs on schedule in debug-out mode / if the LSR stamp still does not update) and sending it to 2BS Support (details in KB article)
-
cliffhanger
- Expert
- Posts: 606
- Joined: Tue May 31, 2011 5:59 pm
Re: No time stamp update to "Last Successfull Run"
PS - I just noticed you are posting in the SyncBackFree section, and strictly speaking freeware users are not entitled to technical support from 2BS, so sending a Support Zip to them may not be appropriate in the circumstances 
However, although I can't exactly give you permission, you could try it and see anyway (the LSR field should be updating - and for me it is - so if still not updating for you (even after pressing F5), it could be a bug, so 2BS might be keen to see evidence either way)
However, although I can't exactly give you permission, you could try it and see anyway (the LSR field should be updating - and for me it is - so if still not updating for you (even after pressing F5), it could be a bug, so 2BS might be keen to see evidence either way)
-
mcneillkj
- Newbie
- Posts: 2
- Joined: Sat Sep 30, 2017 2:43 pm
Re: No time stamp update to "Last Successfull Run"
Pressing the F5 key does indeed update the field thus showing the last update date I expected. Thank you, cliffhanger.
It seems odd to me that one has to manually refresh.
Kevin
It seems odd to me that one has to manually refresh.
Kevin
-
cliffhanger
- Expert
- Posts: 606
- Joined: Tue May 31, 2011 5:59 pm
Re: No time stamp update to "Last Successfull Run"
It's because the copy of SB that ran your scheduled profile (which copy Windows Task Scheduler has closed again by now) is not the copy of SB that you are viewing. A copy of SB run by the Windows Task Scheduler often runs in session-0 (this is decided by Windows, not SB) and is limited (by Windows security) in the information it can pass to any other open copy of SB. If you re-started SB (or, the PC, then SB), you would avoid the issue because SB scans all profiles for latest metadata when it starts up. But if neither the PC nor the foreground copy of SB are re-started in the meantime, you sometimes need to manually ask SB (via F5 or equivalent) for the metadata of all the profiles to be re-scanned.