x Want to participate? Join the group to interact
Sage Employee
Related
Recommended

Pre-Release Notice: Sage 50—U.S. Edition 2020.0

2 minute read time.

This notice provides important information for Sage Accountants Network (SAN) members supporting clients on unsupported versions of Sage 50—U.S. Edition.

Due to a required upgrade to Actian Zen v13 (formerly Pervasive) in the Sage 50—U.S. Edition 2020.0 release scheduled in July 2019, SAN members and Certified Consultants/Partners supporting clients on older versions of Sage 50 or Sage 50cloud will no longer be able to maintain versions prior to 2019, along with 2020, on the same computer.

The Pervasive License Check for Sage 50 US versions 2018.2 and earlier specifically look for a Pervasive version 11 license key.  When you install Sage 50 US 2020.0, Pervasive will upgrade to version 13 Actian Zen on the machine.  As part of this upgrade, Pervasive/Actian makes the v11 keys inactive, leaving the new v13 keys.   This will cause the earlier version of Sage 50 to no longer work as it will not have the proper key.

It is also important to note that Sage 50 2018.2 and earlier versions are no longer customer-supported releases, so this an opportunity to discuss upgrade options with your clients.

 

Why We Are Upgrading from Pervasive v11 to Actian Zen (v13)

Actian Zen v13 better supports Windows 10 and offers better Windows 10 compatibility. An upgrade is in order to receive the updated maintenance that Actian has developed into v13. 

In addition, the updated version of Actian offers improvements to installation which should result in fewer Actian and Sage 50 installation issues.  As well, this version enables updates to activation including a change that should significantly reduce broken keys that today cause the need to reactivate. 

 

What You Can Do Now

In order to avoid any issues when installing Sage 50 2020.0, we strongly recommend that you take necessary action prior to the July release. This includes upgrading your clients to the latest version of Sage 50, acquiring the necessary equipment needed to run the different versions of Sage 50 on separate machines, and/or running Virtual Machines like VMware.

We’d Love Your Feedback

We are always looking for opportunities to improve your experience using Sage50cloud as a member of the Sage Accountants Network. Do you have any feedback on what we can do to enhance Sage50cloud?  You can enter detailed suggestions in the Sage City General Ideas section for Sage50 and even vote on existing suggestions to help us better prioritize where we focus our resources.  

Questions? Join product discussions right here on Sage City, search articles in the Sage Knowledgebase, or contact Customer support for more information.

Parents

  • I have an accountant as a client who supports many local small businesses, who all use different versions of Sage and some who will not be willing or able to upgrade their software to the latest.  My question is regarding doing a network install.  Can Sage 2020 be installed on the same server as all previous versions hosting the company data as long as the client is installed on machines that do not have previous versions installed or would they need a 2nd server?  They will be upgrading their server very soon at which time I could keep the old one in service for previous versions but they are not in the position to do it just yet

  • in reply to RobCarnevale

    Hi RobCarnevale -

    In the scenario you describe the 2020 release would need to reside on a separate 2nd server, the prior versions will not function on the same machine as the 2020 release (with the exception of release 2019).

  • in reply to DonaldC

    Thank you DonaldC for your reply.  I spoke with my client and it turns out the Data they receive from their clients is only used in house and they do not return it so if my thinking is correct I see no reason why they would even need to use different versions, they should be able to just convert the data to the latest version  and can safely remove all previous versions of Sage from their server correct?

  • in reply to RobCarnevale

    Hi RobCarnevale - 

    This is a correct line of thinking, the only caveat is depending on the age of the data they may have to "step" the conversion to an earlier version first.  For example, Sage 50 release 2020 can convert data automatically from versions 2014-2019 but would be unable to convert a data set formatted for release 2013, in this cast the 2013 data would have to be converted to 2014 (or later) first and then converted to release 2020.

Comment
  • in reply to RobCarnevale

    Hi RobCarnevale - 

    This is a correct line of thinking, the only caveat is depending on the age of the data they may have to "step" the conversion to an earlier version first.  For example, Sage 50 release 2020 can convert data automatically from versions 2014-2019 but would be unable to convert a data set formatted for release 2013, in this cast the 2013 data would have to be converted to 2014 (or later) first and then converted to release 2020.

Children
No Data
Generic Content
Generic Content

*Community Hub is the new name for Sage City