Question - I installed the "full" 2020.1 version on a new laptop last Friday.  Will that have the same problems as the original 2020.1 "update"?  I do see that the full version download page has a "last updated" date of 1-6-2020, so it seems to have been replaced as well.

Would I be advised to uninstall the original 2020.1 and download/install the version posted 1-6-2020?

To others out there, I would be interested who has successfully deployed the newest 2020.1 (i.e. did you have problems updating the databases?).

I've downloaded the hotfix but still cannot open my company file in the new year. Has anyone else had this experience? Advice?

Did you install the "hotfix" to the original 2020.1 from last week?  Or are you talking about the "new" 2020.1 that was released this morning (what this thread is about)?

KB102602....I think that's the new one. Don't see anything more recent....

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

The hot fix did not work for me.  Should I uninstall 2020.1 and start over with a new install of your new download released today?  

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

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

Hello ltulloch, if you're still having issues converting your data after applying the hotfix announced Jan 3rd to your 2020.1 version (installed prior to Jan 6th) please make sure that the data is copied on the folder in the C:\\Drive before converting.

If you're still unable to convert, try Method 1 in KB 102392 (See 260-1009048 for French).

If you're still not having any luck then please contact Sage 50 support at 1-888-522-2722.

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.

We usually have data on a virtual drive..... so that is where I am trying to store and convert the data.  further, the program file the .exe is actually saved on an SSD D: drive where I run many programs from as my C drive is pretty full.   Not sure if this is part of the issue, but even after the hotfix, and then trying Method 1 - still doesn't work.  And - when I get to Method 1 - I only have the file without the underscore, there isn't one with an underscore.  And when I select the one without the underscore it still says it wants to convert the data - so that tells me it hasn't converted it.

So I'm still nowhere.   Lynn

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

Hello again ltullochLynn,

The latest release of the Sage 50 CA version 2020.1 full product download (see KB 100797 the file size is 394 MB) is now available. If you're currently still running 2020.0 see below for details on how to run the automatic download of the 2020.1 update. We were successful in converting data. Alternatively, a hotfix patch (see KB 102602 and KB 260-1009050 for FR) was announced on January 3rd, 2020, this is users who installed version 2020.1 and had problems converting data prior to the updated version released January 6, 2020.  

Installing the Jan 6th 2020.1 update on a Sage 50 CA install with version 2020.0

For our example we updated our 2020.0 version via automatic download of the update on Jan 6, 2020.

STEP 1: of this had our company open and on version 2020.0. To bring up the install pop up for version 2020.1 below, we went to the Help menu > Check for product update, then waited for a download complete message to show requesting for Sage 50 CA to be closed. These steps gave the below option to proceed with the install:

STEP 2: Ran the install of update 2020.1


STEP 3: Converted data (located on desktop via C:// drive in Windows 10) and launched the company file successfully.

If you're still having issues, some options to try include:

• Re-installing Sage 50 CA version 2020 using the download in KB 100797 Released Jan 6, 2020

We tried to install the 2020.1 released today, following exactly as Erzsi_I 's instruction; however, we still have the problem "Unable to open the company file".

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.

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

You first 

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

Andywomack do you have any idea as to a timeline for a 100% fix for the Sage 50 2020.1 update?  All workarounds and fixes to date are unsuccessful.

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.

Just come back to celebrate our successful updating. Yesterday, we missed something on Erzsi_l's instruction Step 3 – For network users, we have to copy our sage files to local to convert, and then copy back to the network drive.  Thanks.  All good now.

Jane - thanks for your update, and I guess that's what I'm going to try.

However, we shouldn't have to go through such time consuming work arounds to do a standard update.  These problems are highlighting poor, out-dated architectural designs in their system, and inadequate QA testing (this wasn't an "one in a million" type of situation, the problems were occurring for a very typical client-server configuration).

Thank you Jane Sun for confirming that a local conversion worked for you.

JoeSchwarz Here's a resource on configuring Sage 50 CA for a server environment with insight on issues when trying to open data on the server from a workstation & a read-only or permissions error.

We also recommend working with a certified consultant partner for updates and upgrades in a networked environment. JoeSchwarz I will pass along your comments regarding testing..

All right, so I was able to update a database I copied from the server to my local C: drive from 2020.0 to 2020.1, and I was then able to open it on the client.

Can I assume than my final step is simply to copy the data files back to the same location on the server?  Is there any "trick" to this, like do I need to temporarily turn off Connection Manager or something?  Obviously my users will need to stay off until it is done.

I guess from now on part of the update process will need to be to do the conversion steps on a local computer.  Wonder if Sage will include that in their "official" update instructions from now on?

Here's what I did: I copied the nextwork sage file folder (which contains the .SAJ folder and .SAI date file) to local desktop, rename the original file folder name.  After conversion on local drive, copy the Sage file folder back to the same location on the server.  Delete the renamed old folder on the server after testing everything works fine.