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?  

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.

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

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

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

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.

I don't see how using a consultant would have helped me avoid a bug in the Sage installation - it would have just been them in this forum instead of me.  I've been doing Sage updates here since 2016, the procedure isn't new to me. 

I wouldn't mind handing over to consultants the problems caused from vendor mistakes, except that gets me out of touch with keeping the systems up to date that I'm responsible for.  In this case, I'll be updating my "Sage Update Process" notes to indicate the database update was designed to work directly from the local user's permissions, rather than a server service (this is what I'm alluding to regarding client/server architecture - clients should merely need rights to use the service, while the service itself has the actual permissions to networks, data, etc.).