• Sage 2013 to Sage 2022 wants a version between 2014-2015??

    In the process of upgrade to Sage 50 Premium 2022 from Sage 2013 Premium. I've installed the new software, updated the connection manager on the file server and all seems well. When we try to open a file, we get the error: Since I don't have a copy…
  • Error during upgrade of company to 2023.1

    Hello, We've been trying to upgrade our 2022.4 company to 2023.1, and it fails at step 14. We tried to upgrade another (smaller) company, and it worked fine. It seems like it could be related to the size of the database? See the screenshot below of the…
  • Upgrading to 2023

    We are looking to upgrade our 2022 files to 2023 prior to December 31st. This is our second year using Sage so we haven't gone through an upgrade yet. If we upgrade the file to 2023, are we able to still process 2022 financial information and payroll…
  • Upgrading to 2023 won't save to shared

    Good day, just upgraded my 2022. It's connected through 365 AND is shared for my accountant. I was able to successfully connect after using the 7 character password. But now, whenever I try to exit, to save, to stop sharing, to suspend sharing, it gets…
  • Multiple version installs on same PC

    I am sure it has been asked myriad times before, but is it possible to install two versions of Sage 50 on the same PC? For example, I have a client with Sage 50 2014, that wants to install their copy of Sage 50 2020. If I install v.2020, will that upgrade…
  • Options for moving on-premise Sage 50 CA to virtual private server e.g. Azure?

    We currently have an on-premise installation of Sage 50 CA. We're in the process of moving most of our infrastructure to Microsoft Office 365 and would like to no longer have any on-premise server computer. For the near future, the Sage 50cloud offering…
  • Windows Server 2019 and Sage 50 2019 issues opening files on the new server

    Having issues with accessing company files from our new Windows server 2019. Firewall is off, Sage 50 2019 is installed as server installation. The error that I receive on the workstations is; The Connection Manager could not start the database engine…