Browse By Tags

  • Sage 2018 and Fixed Assets 2023

    Just upgraded Fixed Assets to 2023 for a client and they are still using Sage 2018 (in the process of upgrading to 2023 just waiting for a new server) and now they cannot print in Sage or in Fixed Assets. Getting this error. Report file C: ProgramData…
  • 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 from Sage 50 2015 to 2018 - issue! ERROR - "Previously installed in c:/Program Files (x86)/Sage 50/"

    My old system approached retirement, so I bought a new laptop. I used to run Win 10 but the new one has Win 11. I transferred my files and backups to the new system. Installed my Sage 50 2015 version, and tried to update using CPUPx2018. That is what…
  • Sage 50 Pro Accounting will not convert from Sage 50 Complete Accounting 2013

    Totally disappointed. I have been using this product since the Peachtree days 20+ years. Never had need for all the bells and whistles of the upgrade every year. Last I was using the Sage 50 Complete Accounting 2013 on a computer with Windows 7. Finally…
  • BLOCSTACKED Non-existent strucure member Error

    Hi, Has anyone seen this error before or have any idea what the cause may be? I have started getting this error every time I log in following a failed V12 Patch 22 upgrade. Everything looks OK in the console but the X3\TRA folder contains many…
  • Migration From Sage Accpac ERP 5.3 with Pervasive 8 to Sage 300 ERP 2018 with SQL Server 2017

    I have a Sage Accpac ERP 5.3 using Pervasive 8 but we want to migrate to Sage 300 ERP 2018 using SQL Server 2017 someone knows the best way and best pratices to do it please
  • Intelligence Reporting not working after upgrade

    Hello, I recently upgraded the Intelligence Reporting software on one of our network client machines from version 2.0 to 2.2. I was told by Sage support that I would be able to upgrade by clicking the prompt to install the latest version when trying to…
  • Error: The TimeCard module needs to be reinstalled

    In upgrading a customer from 2015 to 2017, I am getting this error when trying to convert the company: "Error: "The TimeCard module needs to be reinstalled." ID90364 doesn't apply. This company has never had TimeCard so I can't delete it.
  • Missing with GL account folder and Administrative services functions

    Hi, I installed a fresh copy of SAGE 300 2018 and loaded sample data. It is fine with everything. But after loading customer earlier version data and upgraded, I am missing with Administrative services (except data activation) and GL account folder. I…
  • Sage 50 2017.x expired; looking at Sage One?

    Hello, We've been using Sage 50 workstation for a few years now and the time has come to renew for another year at a cost of about $700. This is when I noticed that Sage offers a "Sage One" online product. I've searched some Sage sites and Knowledge…
  • Upgrade - Bank Transaction Header. Invalid list choice put to field 'Reconciliation Status'

    Hi, We are testing an upgrade of a customer from Accpac v5.6 to Sage 300 2018 (v6.5). Everything straightforward but when running a Data Integrity I get a lot of errors just in Bank Services with this message : E: Bank Transaction Header. Invalid list…
  • Timeslips 2017 6 user upgrade from 2014 - some suggestions for a smooth conversion

    I am writing this post in the hope that it will be of help others performing Timeslips upgrades on Windows server environments. I ran into data conversion issues (could not load stringtable resource ID:21999), placed a tech support call from the client…
  • Not updating/ Can't open Company File

    We are running Sage 50 Pro Accounting 2014. We have all the files necessary (SAI and SAJ), it has been narrowed down to when we open the SAI for the company file it says it needs to upgrade to open the company file. We tired to open a backup file…