x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 18 replies
  • Answers 2 answers
  • Subscribers 5 subscribers
  • Views 5688 views
  • Users 0 members are here
Browse Forums
Announcements
764
topics
17
replies
Financial year end
78
topics
177
replies
General Discussion UK
7k
topics
19k
replies
General Discussion Ireland
175
topics
311
replies
Install your software
137
topics
375
replies
Making Tax Digital
286
topics
692
replies
Manage your VAT
147
topics
321
replies
Protect and repair your data
43
topics
136
replies
Run your accounts remotely
85
topics
197
replies
Working with the bank
114
topics
292
replies
Edward Shaw

Why has the way v28 handles data corruption messages changed?

SOLVED
Posted By

If data corruption was discovered by the scheduled backup in v27 then the first user that logged in would get the message that errors have been found in the data. Once the recovery tools had been run no-one would receive this message again until the next time the data is corrupted.

In v28, when data corruption is discovered by the scheduled backup and after the recovery tools have been run, every user who logs in to the system will get the message that errors have been found in the data and these messages will continue until the next scheduled backup runs with no errors.

So lets say I come to work in the morning and login to Sage and get the message that there are errors in the data. I then login as manager and run the recovery tools which ends with a data check showing no errors. I then login as a user and I get the message saying that there are errors in the data. Then I have to inform all my staff that although Sage is reporting errors, actually there are none because it has been fixed.

How is this progress ? In my opinion a bug has been introduced into these error notification messages.

  • 0
    SUGGESTED

    Hi Edward,

    This doesn’t seem quite right.

    The message should clear on all machines unless they’re connecting via remote data access. The same behaviour as v27.

    There were changes in this area but this isn’t what I’d expect.

    I’m on holiday at the moment but will test this and get it logged as a bug if it’s not working when I’m back next Tuesday.

    I’ll push for it to be fixed for v28.1 due in sprint 2022.

    The workaround you’re using at the moment with schedule backup will work in clearing the error on start up.

    Kind regards,

    Ian

  • 0 in reply to Ian C

    We have run into this problem today, although is V28 not treating everyone like remote data access users?

  • 0 in reply to Andrew Cooke

    Yes and no.

    If you're using Remote Data Access with v28 all sites will be "online" however if you say have 3 users in the office that are connected to the local area network they'll still be connected to their own Sage data service.

    If the 3 users in the office get the error message on startup and fix the problem, then they should no longer see the error message when they login but if you have a 4th user working outside of that local area network they would see the error message until they either ran check data or schedule backup.

    Interested to know your your setup and problem as i'm keen to fix this if it is wrong.

    I've tested this with comments but i've not been able to re-create the problem on a local network.

  • 0 in reply to Ian C

    Just done it, fixed the error on a remote data access computer last night. This morning networked user 1 logged in error messaged displayed. Checked data no errors. I logged in as user 2 networked error display message showing. Logged out, logged back in as manager error message showing while on with your help desk. Did check data no errors.  All 10 locally networked users have had to check data to clear the error message.  

  • 0 in reply to Andrew Cooke

    When you fixed it on the remote data access computer, can you remember how you did it? Did you press "Run Repair" on the startup message OR did you click "Run Repair" via the check data screen OR did you use Recovery tools?

    Just to make it a bit more confusing, the three fixes are implemented in different ways. 

  • 0 in reply to Andrew Cooke

    OK thanks very much.

    I'll set this up later today and see if i can re-create it. I'll report back with the results.

    As a workaround on the network machines that have the problem, log in as manager and go to File > Schedule backup > settings and set the check data to run at a convenient time.

    This will clear the problem.

  • 0 in reply to Ian C

    Every time any networked terminal logs in at the main site, it reverts to saying there are errors, check data says there are none.  The remote users (tested the same user local and remote) are not showing the error message.

  • 0 in reply to Andrew Cooke

    Hi Andrew,

    I've tried this a couple of times this afternoon but as of yet not managed to recreate it.

    I've set up a computer as my local network and uploaded my data. I've then connected to a remote site. Both sites get the message on startup about corruption and I've fixed the data on the remote site using Recovery tools.

    At this point, the remote site has no errors and no message on startup. If I log into the local network computer it gets the message on startup (expected) but when I run check data on that machine, it shows no errors, and when I restart the machine it shows no errors on startup.

    Is there anything you're doing differently? 

    Ian

  • 0 in reply to Ian C

    Morning, After having spoken at length to one of your colleagues I understand this feature has been designed into V28. However its perplexing it is that this has passed even the idea stage at sage, a warning light should always be acted upon not ignored.

*Community Hub is the new name for Sage City