Downloads for Sage 50— Canadian Edition

The Sage 50 2020.1 downloads have been replaced.  See KB 100797 for the full product download and KB 102293 for the product update. Please remember that the hotfix for customers who have already downloaded and installed a 2020.1 update prior to today is available in KB article 102602.

Parents
  • I have not installed any of the updates yet,  I saw Alert and decided not to update yet.  So my question now is I am not sure if I download the Full Product Download or the product update.  I currently have 2019 Sage 50 Accountants Edition (Release 2020.0)

    Thank You

  • in reply to Tax Town

    I suspect you would want to do the "update" if for no other reason it would continue on with the license information you have already provided for 2020.0, and maybe any "preferences" you have already set up (I'm not a user, just the guy that installs for the users, so I don't know if the latter applies).

    I'm at the exact stage you are, and to be honest I'm waiting for somebody else to be the "guinea pig" tester.  :)  Would be a little reassuring if the original post in this thread had said something like "we identified the causes for the issues in the original release and have fixed them" instead of simply stating "downloads have been replaced". 

  • in reply to JoeSchwarz

    Thank You Joe,  I think I am waiting a bit still too.  Not worth the headache.

  • in reply to JoeSchwarz

    Yeah - but having already installed the update once, I'm kind of assuming it's likely problematic.... not sure that it will just overwrite it.   I'm with you.... kid of waiting for someone to tell me exactly what works.   Luckily we run this on 2 machines, and I only tried converting on one machine with a smaller holding company files..... our main files are still working in the original 2020.....  but I really need to get the other machine working again asap.  But I'll just chill today and see if anyone else can confirm what to try next.

  • in reply to JoeSchwarz

     yeah.... I don't have to do payroll until next Monday....so you all give this a go and let me know  Slight smile

  • in reply to JoeSchwarz

    I called today and they told me everything was good to go and running perfectly. Now can someone tell me how to install the update? I am drawing a blank.

  • in reply to Larco

    go up to the top  Help - then choose "check for product updates"  frm drop down  - can you come back and tell us if this update really did work?  thx

  • We have been working on completing this update for a few days now.  Every time Sage releases a "fixed" version of the update (including the most recent), the process fails.  We've tried everything that we can find with respect to workarounds (hotfix, copying the files to the local machine, local account vs domain account, etc, etc.) with NO success.  Yes the firewall changes have been made and yes the antivirus is disabled.

    i find this absolutely astounding that this is continuing with no resolution yet...

Reply
  • We have been working on completing this update for a few days now.  Every time Sage releases a "fixed" version of the update (including the most recent), the process fails.  We've tried everything that we can find with respect to workarounds (hotfix, copying the files to the local machine, local account vs domain account, etc, etc.) with NO success.  Yes the firewall changes have been made and yes the antivirus is disabled.

    i find this absolutely astounding that this is continuing with no resolution yet...

Children
  • I wanted to test going through the upgrade process from 2020.1 client on a copy of my production database.  I tried opening this 2020.0 database, and I get the error that my server must upgrade to the 9.1 version of Connection Manager (i.e. the version that comes with the 2020.1 update).  I don't want to commit my server to that version yet, not until I get better assurances this will work.

    Erzsi's "test" of running the update against a database on the C: drive does not match my production environment of having the database on a shared server folder mapped to a different drive - which seems to be where the problem occurs.  Sage's testing of a fix should match the environment where the problem occurs.  What would assure me is someone who has successfully run the update in a typical client/server environment - it's a little disconcerting when even Sage support has not categorically stated they have run such a test.  If the "work around" is that I must update the files on the local C: drive, then at least follow through and let me know that after I do that, is it simply a matter of copying the updated SAI file and SAJ folder back to the original server folder and we can proceed normally from there?

    I tried setting up a "test" server that I can run through the process without endangering my production data, but I'm getting an error about the database files being "read only" (I opened a separate thread about that in the Installation support forum).  The only other way I can think of to do a "trial run" is if I could run both versions of Connection Manager on my production server, such that my users could continue with 2020.0 while I test with a 2020.1 client - is that possible?

    I really feel like I'm doing Sage's QA work for them right now.