Why is my Sage 300 CRE Software so slow?
One of the complaints that Sage 300 CRE users voice the loudest is slowness in the performance of the software. There are some main causes for performance issues and these Knowledgebase articles will help you speed up your Sage 300 CRE software! (You must log into the Sage Customer Portal.)
Nine ways to speed it up!
1. Antivirus or anti-malware security software actively scanning the data or software.
See articles 32849 (Why is Sage Estimating or Sage 300 CRE so slow?) and 17258 (What Sage 300 Construction and Real Estate and Sage Estimating files and folders should I exclude from my antivirus software scan?).
2. Malware or virus infections not caught by your antivirus or anti-malware applications. See article 24542 [Slow performance of Sage 300 Construction and Real Estate and Sage Estimating (virus or malware infections)].
3. Network issues (network adapter duplex/link speed settings, latency issues caused by faulty hardware or software).
See articles 33869 (Slow performance in Sage products (incorrect network adapter duplex settings) and 31213 (How do I use the PING command to troubleshoot network connectivity?).
4. Hard drive failure or imminent failure (i.e., hard drive going bad). Symptoms generally include Windows Explorer lagging, not responding, icons and files/folders taking a long time to display, corrupt files (CRC errors), Windows complaining about SMART errors, BIOS or POST SMART errors.
Contact your IT professional for assistance. See article 61349 (Slow Performance in Sage 300 Construction and Real Estate or Sage Estimating (hard drive failure imminent))
5. The server or workstation not meeting minimum requirements, or meeting minimum requirements but having the additional load of performing many other tasks. For example, your server or workstation meets the minimum requirements, but you install dozens of other applications that tax the processor, RAM or hard disks, and the minimum requirements will no longer apply. Keep in mind the minimum requirements are just the bare minimum. If the server or workstation is intended to perform other tasks, you must have computers that meet or exceed the recommended specifications.
See article 61353 [Slow performance for Sage products (Sage 100, Sage 300, Sage Estimating – computer does not meet requirements)] and requirements set forth in the installation or user guides.
6. Incorrect workflow used during the Sage 300 server migration, incorrect workflow used to delete company folders, or the server crashed prior to a migration.
See article 25496 [Slow performance of Sage 300 Construction and Real Estate after migration (company folder list takes a long time to load)].
7. Your Sage log viewer is large (2GB+ in size), or you are running Sage MyAssistant, and you have tasks that are set to run “At the conclusion of a Sage 300 CRE program,” such as the option for “Run the task each time this Sage 300 CRE process completes.”
See article 19543 (How to archive the Log Viewer).
See article 19542 (Starting the MyAssistant ISDAdminTaskService slow entire server)
8. The Sage Event Log may not be functioning correctly. You can access through the Windows Event Viewer to verify if there are recent entries. Background Tasks and other Sage processes may not function well or at all if this log isn’t updating correctly.
See article 34486 (Sage System Verifier fails on Windows Event Log sources).
9. If only one or a few reports are affected, the way the report was designed (how it accesses and sorts data) may be the cause.
Contact the person who originally wrote or customized the report for assistance troubleshooting the report design.
Related article: Backups are Critical Against Ransomware Viruses
Submitted by Kyle Zeigler, Sage Senior Certified Consultant