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 5675 views
  • Users 0 members are here
Browse Forums
Announcements
763
topics
17
replies
Financial year end
78
topics
177
replies
General Discussion UK
7k
topics
19k
replies
General Discussion Ireland
175
topics
310
replies
Install your software
136
topics
374
replies
Making Tax Digital
285
topics
691
replies
Manage your VAT
147
topics
321
replies
Protect and repair your data
43
topics
135
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.

Parents
  • 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

    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.

  • 0 in reply to Andrew Cooke

    Hi Andrew,

    Unfortunately, I've not managed to re-create the issue you're experiencing.

    v28 has been available since early October and each day customer service will update the product development team on any new issues that have come in. So far this one hasn't been flagged to us as a problem and as such hasn't been investigated other than the conversation I've had here.

    That individual feature alone went through 700 hours worth of testing, so i want to reassure you that steps were taken to make sure it worked but with all software sometimes things can be missed.

    If new information comes to light then I'm happy to test any new scenarios but at the moment it appears to be working for me.

    Ian

  • 0 in reply to Ian C

    Ian - this is just not correct. All the people I've spoken to in Sage support are aware of the problem and some of them have suggested a temporary work around.

    The advice is that after running the recovery tools - we should change the scheduled backup time to be in 5 minutes after the current time for example. Wait until the scheduled backup and check has executed and then put the time back to where it should be.

    While I accept that the new version has been available since October we only upgaded two weeks ago and we ran into this within one week of upgrading.

    There is the point that if you don't often get data corruption then you won't see this - but we get data corruption at least once a week but that is another issue.

    I contend that Sage personnel are fully aware of this issue and I'm afraid I don't accept that you can't replicate it. All you need is Sage data on one machine and to log in from another networked machine. Clear the errors as manager and then log in as a different user - the errors will be reported again.

    If this feature has been changed by design as you suggest - what was it the intention to achieve?

  • 0 in reply to Edward Shaw

    Ian, I agree with Edward and the conversation I had yesterday that will be continued at 11am today with your colleagues proves Edward and I are correct.

    Sage need to do some real world testing. Had you requested I could have let you log in yesterday to see the fault before the scheduled backup cleared it at 5pm.

    What you have purposefully designed in sage is equivalent to the below in cars:

    Low Oil light comes on

    Customer : refills the oil

    Low Oil light stays on, 

    Car manufacturer: We will clear it at the next service.

    Customer effectively told ignore the low oil light

    car breaks

    Car manufacturer: but there was a warning saying there was low oil

    Warnings should ONLY ever be active if you need to act otherwise everyone ignores them.

    We updated 1 week ago today. 

  • 0 in reply to Andrew Cooke
    SUGGESTED

    Some context on the feature, we know that nearly half of corruption is fixable but customers don't know what to do when they get corruption

    So in version 26 we introduced "Run Repair" which meant that you didn't need to know which "Recovery Tool" to press, you simply click Run Repair and it automatically fixes it.

    This has worked well but we found that customers weren't getting to the "Run Repair" button because they were scared of the message on startup and unsure what to do. This message essentially tells you to run check data.

    in v28 we wanted to improve this, so if you get corruption the message on start offers you to "Run Repair" rather than asking you to run check data.

    Advantages of this
    - Message nice and clear
    - We automatically take a backup for you 
    - We automatically fix the data 
    - No user input
    - We restore the broken backup and mark your data as unfixable if it fails to repair.

    Important to note that you'll get the old message if the data isn't fixable or requires the user to do some extra steps.

     I've followed your steps and attached a video below, if I'm doing something wrong, please correct me. (2 Computers both networked, schedule backup runs, i show that both machines are connected and have corruption and one user fixes it with recovery tools. I then show all messages are cleared)

    https://youtu.be/DFDxOaG9las


    It could be that your data has some kind of error that is causing this to fail, again i'm keen to investigate. Feel free to email you the backup of your corrupt data and i'm happy to look into that. 

    Ian

  • 0 in reply to Ian C

    Ian - in the video you seem to have a different screen to me. I don't see the option to repair data. I can't show you now until we get errors again and then I'll take a screenshot.

    Our error is almost aways:

    'Total allocated disagrees with total allocated in stock files'

    So we run recalculate order allocations and recaluclate project history.

  • 0 in reply to Edward Shaw

    No problem.

    I would be really interested in seeing the message you get, so feel free to post the image on here or send me a screenshot.

    Also if you want to send me your data from a time you had corruption that would also be useful.

    I know Andrew has been speaking to my colleague today, which I've been updated on.

  • 0 in reply to Edward Shaw

    I don't have run repair on any of my Sage 50 v28 companies either and I have the same issue as you where but every user that logs in after I fix a data corruption error still gets the message about errors. I have all my companies set up to run a check data and backup at 11pm at night.

    I also have the opposite issue where a overnight check data picks up errors and the company gets used the next day with no message about errors until they run a check data and backup when finished working.

  • +1 in reply to Pamela Dillon
    verified answer

    You'll not get "run repair" if your data is to badly damaged.

    If you install v28.1 the issues discussed in this chat have been resolved

    www.sage.co.uk/au

Reply Children
No Data

*Community Hub is the new name for Sage City