• Sage 2023 Upgrade SP3 attempted reverted back to Sp1 with no SQL security integration Issues

    I upgraded a client from 2022 to 2023 SP3 at the time with the SQL security integration and had issues. So I restored the data, uninstalled V2023 Sp3 and put SP1 on with no integration. Now we are running into issues with BI and Customer account code…
  • 2023 PU5

    New issue with this database vault and store. This is so frustrating. I've done a few of these now and I have creating the store and vault databases and vault user down pat. I am upgrading a client from 2023 PU1 to PU5, have created the pre-requisites…
  • Sage 300 2023 Pu3

    Hi We have currently decided to hold off installing Sage 2023 pu3 until we are more familiar with the implications. We are only loading Pu1 at this stage until we can better assess the security enhancements. This statement is of particular concern…
  • CANNOT ACTIVATE COMMON SERVICE DATA - SAGE 300 2023 PU1

    I have active companies on this version, but I want to activate new company profile. I got an error The user Input E-mail Password cannot be blank.
  • Is Sage 300 version 2020 supported with Microsoft Server 2022?

    We are planning to upgrade Windows Server not Sage 300 2020 yet and wondering is Sage 300 version 2020 supported with Microsoft Server 2022?
  • "A problem occurred and a valid license for this product cannot be found" after installation of PU7 and 1099 update

    Hi, We are having to re-install Sage in all our workstations due to this problem. Does anybody know if there is an easier way to get this to work? Is there any way to prevent this with the PU7 update? Ty.
  • Outdated version of XML5 flagged by our recent audit

    We have some computers in our organization that have an outdated version of xml5. The only things all of these computers have in common is they have Sage 300 and PrintBoss installed. Can you confirm that xml5 is installed with Sage and if it is, how do…
  • Client was on Sage 300 2018 PU3 - Got the error that the license had expired, but they were current.

    Upgrading to PU 6 to put the 2020 sm license key in we attempted to put in the new license, all sage-authentication accounts with admin rights lost their module access. Normal windows authenticated users seemed okay, and the default Admin account seemed…
  • Error 53 after upgrade from Sage 300c Premium 2017 to 2019

    We are getting "Error Code: 53 File not found." in Purchase Orders only, after an upgrade. Clicking OK allows us to continue - don't see any other errors. Happens only when creating a new PO, upon entering a vendor and entering the first item onto the…
  • UI container stopped working when reviewing report, after PU3 installation of 2018.

    Hi, I installed PU3 for 2018 and after that, UI container stopped working message appeared on each of print function. It crashed when it went to preview screen. Does anyone has any idea? OS: Windows 2008 R2 SP1 - Terminal Services SQL: SQL2012…
  • Product Update 3

    After installing product update 3, all AR and AP programs do not load. We get a an error box with the following 3 errors: 1. Error occurred when opening view AR0048. 2. View 'AR0048' is not avalid view ID. 3. Error occurred when activating Sage…
  • Product Updates for v6 AccPac - SQL

    We have a customer running v6 PU1, and we're getting ready to move (finally) to v2017. We need to get them to whatever the last PU for that version was and neither they nor we have those patches. They're not available on the KB. Anyone have them somewhere…
  • Error: "Unable to modify CPCHKD"

    Hi, I have this error message when converting Payroll in Sage 300 ERP "Unable to modify CPCHKD" went through the following steps and not solved. Rename the SQL database for the company in question, and set up a new SQL Database with lots of extra…
  • Sage 300 2014 ERP PU1 and PU2 works on Microsoft Surface with Windows 8.1 Pro

    One of our customers V.P. of sales has a Microsoft Surface with Windows 8.1 Pro. 2/3/14 SAGE 300 ERP PU2 loads but fails on connecting to company. The customer tried repeatly to remove Sage 300 2014 PU1 and re-install Sage 300 PU2. we opened a case#8004272818…