Post V32 upgrade critical error

Suggested

I have just upgraded to V32 and all appeared fine EXCEPT - on ad-hoc occasions - when i exit a data set i receive a "Critical Error" message.

There doesn't *appear* to be any corrupted data but it IS VERY worrying!!??

  • 0
    Suggested

    Hi Kessie,

    Is there any other wording alongside the Critical Error message?

    Critical error messages can appear if you're working with a large amount of data, and can be resolved by some data management, there's more in this article: Error - A critical error has been encountered

    Andy,
    Sage UKI

  • 0 in reply to AndyR.

    The full message is: "A critical error has been encountered in Sage 50 Accounts. To avoid damage to your data the program will now close".

    This happens infrequently and only ever when i am exiting the data set!!??

  • 0

    Hi Kessie

    Hope your problem has been resolved?

    We have just upgraded to V32 and I got the same.   I had to install 32bit software though.

    We were advised to clear some older transactions to reduce our audit trail.  its odd never had an issue before the upgrade.

    it seems to be intermittent but was falling over when looking at bank activity.

    just wondering how you have gotten on.

    thanks

    Fiona

  • 0 in reply to FionaSage

    Hi Fiona, as you say - it's intermittent and yes, it's still occurring. I can't see any particular regularity to it other than it happens (invariably but not every time) after i have just run a back-up. MORE than a tad stress-fueling!!

  • 0

    It is worth noting that you do not have to install the 32-bit version of Accounts purely because you have add ons that are 32-bit. A 32-bit add on should be able to seamlessly work with the 64 bit version of Accounts installed. There can sometimes be issues with anti virus software interfering with this interoperability but as a general rule an add on should work OK with 64-bit Accounts.

    In terms of the critical error it is unlikely to be related purely to having installed the 32-bit version installed. However if you wanted to test that theory you could always uninstall the 32-bit version and install the 64-bit version to see if it make any difference. The data would be fully compatible so there should be no great risk to doing this, even if the 32-bit version is still installed on other machines on your network.

    Hard to say exactly what the true cause of the issue is, but I would recommend contacting support as they would hopefully be able to collect addition details, such as a crash dump file, that would provide greater insight as to a root cause.

  • 0 in reply to Darron Cockram

    Hi Darron, i'd love to say that was REALLY "helpful advice". Unfortunately i'm a complete techno-dinosaur and a sole-trader (i.e. no "IT Dept)! It's all more-than-a-bit beyond me. i did ask Support but as it's not consistent they couldn't offer much assistance.

    It's a bit like tooth-ache and getting to the dentist just as it disappears!!!! Kes. 

  • 0 in reply to kessie
    Suggested

    Hi Kes,

    I'd certainly recommend giving Sage Technical Support another call, you could refer them to this conversation for reference. They will be able to help you install the 64 bit version to see if that resolves the issue, and they can look into crash dump file that Darron also mentions.

    Sage Technical Support

    Andy,
    Sage UKI

  • 0 in reply to AndyR.

    Thank you Andy. ALL assistance sincerely appreciated.....K. x

  • 0 in reply to kessie

    I am going to have to monitor our crashing issue here but so far so good this week.    hope thing settle down for you.

  • 0 in reply to Darron Cockram

    Hi Darron.    I was advised by the support dept of our 32 bit software that I had to replace our sage 64 bit with 32 bit.   they are obviously being cautious about it....