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". 

Reply
  • 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". 

Children
  • 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...

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

  • in reply to JoeSchwarz

    Hi Joe, have you tried the update yet?  I'm still very scared to try it. I just need to do an update as per my above comment.  I have not attempted anything yet.  Your advice would be greatly appreciated.

  • in reply to Tax Town

    I'm doing our update in a couple of hours.  If you do what I plan, which is to run the update against a *copy* of your production data files on a local drive, and if that succeeds simply copy the updates back to the original location, there should be no risk.  Worst case scenario is that the update on your local copy fails - in which case your people keep using the previous version.  If you keep your previous data files in some backup location, you will have a "roll back" route in case of failure.

    Just do your initial update on a computer that your accounting users don't use, so you are not changing anything in "production" until the update is proven successful.  And again, make sure you are logged in as an Admin on that computer.

  • in reply to Tax Town

    I just finished the update and everything seems fine (my bookkeeper just logged on to her computer and is using it).  HOWEVER, my first attempt failed, I got stuck on "Overall Progress 12/30" for about 30 minutes, and finally ended with the error message about the update failing.  But I realized that I had forgotten to "Run As Admin" (I just did the standard double click on the desktop icon).  When I tried a second time I corrected this mistake and it all went very smoothly, only took a few minutes.

    After I updated the local files, I then renamed the files on the server (prefixed them with "OLD"), then copied over the updated files.  Then I updated the server (thank god no reboot required), and after that I was able to open my multi-user database on the server like normal.

    Just to see what would happen, I then did the upgrade to my test database that was still on the server (I didn't copy it over to a local drive first), making sure to use "Run As Admin".  This succeeded just as well, so this whole "Sage prefers to do updates on the C: drive" seems to be a red herring, the problem seems to have always been about running the EXE at an elevated level.

    Something interesting to note, in my first failed attempt I found a log file that had been created which was named today's date and the time I was doing the install.  It contained meticulous entries of everything it was updating, i.e. every form, every database update, etc.  About a quarter way through it started listing SQL statements, apparently trying to get record counts of every table.  After each one there is an error about not being able to connect to any MySQL hosts.  After that it lists for every table an entry like "Table did not exist after upgrading to MySQL 5.7.27".  These entries covered about a half hour span of time.  Since the installation is obviously able to detect such errors, you would think it would start displaying error information to the user, or even just abort the install (some of those tables are obviously going to be crucial and there's no point in proceeding without them).  Instead it just displays a useless progress bar for 30 minutes, long after the update was doomed for failure.