Initial questions which may help to isolate areas of focus:

• Exactly where, when, and for whom does the slowness appear?
  • During initial login?
  • Prior to the appearance of the Logon window?
  • After Logon and prior to the Company List?
  • After selecting a Company?
  • Specific application(s)?
  • Specific task(s) or report(s)?
  • Specific company data folder(s)?
  • Specific workstation(s)?
  • Specific terminal server(s)?
  • Everywhere except for the file server?
  • Everywhere including the file server?
  • Specific user(s)?
  • Only in CRE 300 Applications or in all programs on the computer(s)?
  • Performance tab of task manager, how much ram is free?
• Is your slowness consistently reproducible or sporadic/random in nature?
• Chronologically speaking, when did your slowness begin to appear?
• Describe the nature of the slowness with as much detail as possible, indicating the actual time to complete compared with the expected or previous time to complete
• When was the last time you rebooted the server?
• Is there a restart schedule for the server and terminal server(s)?
• When was the last time you rebooted the workstation?
• Are you collecting backups while users are actively working? Shadow copy? Pervasive/Actian Backup Agent? VM Backups or Replications? Other?
• Is Record Security or File Security enabled in CRE 300 Security Administration?
• Have there been any changes between when it was not slow and now?
  • Upgrade?
    • Current CD Version, Revision, and Update?
    • Prior CD Version, Revision, and Update?
  • Migration?
  • New software?
  • New hardware?
  • Recent virus or malware infestation - even if you believe you have cleaned the virus (damage may already exist, or infection still exists)?
  • Recent crashes?
  • Windows updates?
  • Antivirus/Antimalware updates or changes?
  • Additional network protocols?
• If you perform the same steps in a test environment or sample data, do you get the same results?
• Is your server low on drive space?
• Is your workstation low on drive space?
• If you install Sage products on a new computer or a newly reformatted hard drive, is the performance still slow?
  • Note: The correct method of troubleshooting by installing Sage products on a newly reformatted computer or a new computer means that after obtaining a clean install of the operating system:
    • Do not start installing all your other software such as antivirus etc.
    • Do not join the computer to the domain if you have domain policies that start installing Windows updates automatically or start installing all your other software automatically
      • Instead, after obtaining a new computer, install Sage products to verify if the performance issues are present or not. Once identified, continue with your normal installation process of other software or joining the computer to the domain, etc. This will identify if a specific piece of software, Windows update, or group policy is part of the cause
• Is the Log Viewer file (master_qlm folder inside 
  
  C:\ProgramData\Sage\TIMBERLINE OFFICE\9.5\ACCOUNTING\Global\PVData on the server
  ) over 2GB in size?
  • Interfacing OEMs and 3rd party programs can cause the QLM file to grow quickly because syncing/connecting login/out entries are constantly recorded in the log viewer
  • You should archive or move the Log Viewer when it approaches 2GB in size.
• If after going through this article and you still cannot isolate the cause for slow performance issues, contact Sage Support for a more thorough investigation
• Performance issues can take a lot of time and resources to identify the root cause
• Be prepared to have your answers to these questions and more when contacting Sage Support
• Have both the IT party and the affected main user on the call

Two main causes of performance issues:

1. Antivirus or other anti-malware security software actively scanning the data or software
   • See Why is Sage Estimating or Sage 300 CRE so slow? and What Sage 300 Construction and Real Estate and Sage Estimating files and folders should I exclude from my antivirus software scan?
2. Log Viewer file (master_qlm folder inside master_qlm folder inside 
   
   C:\ProgramData\Sage\TIMBERLINE OFFICE\9.5\ACCOUNTING\Global\PVData on the server
   ) is very large (over 2GB in size)
   • See How to archive the Log Viewer for instructions on archiving the Log Viewer
   • If it is too large to use the archiving feature in the Log Viewer, you can move the master.qlm file using File Tools. See How do I move or copy files using File Tools? Note: When selecting the master.qlm file in File Tools, you will need to browse to the Global folder (default location is on the server 
     
     C:\ProgramData\Sage\TIMBERLINE OFFICE\9.5\ACCOUNTING\Global\
     ) to locate it
   • IMPORTANT: To slow the growth of the file, it is recommended to turn off (unmark) logging for the Security log type in the Log Settings. This will stop the recording of the log in/out entries. Log Settings can be accessed one of two ways:
     • Sage Desktop, Common Tasks, Log Viewer, then click Settings from the toolbar
     • Sage Desktop, Options, Security Administration, Log Settings

Other reasons for performance issues:

• Invalid company references in the CPL file (Call in for phone support for help with this)
• Replicator instance name file in MISC folder if you do not use Replicator
• Your Sage log viewer is large (2GB+ in size), 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 Starting the MyAssistant ISDAdminTaskService slows entire server
• Malware or virus infections not caught by your antivirus or anti-malware applications
  • See Slow performance in Sage products (incorrect network adapter duplex settings) and How do I use the PING command to troubleshoot network connectivity or slowness?
• Hard drive failure or imminent failure (i.e., hard drive going bad). Symptoms 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 Slow Performance in Sage 300 Construction and Real Estate or Sage Estimating (hard drive failure imminent)
• The server or workstation does not meet minimum requirements or meeting minimum requirements but has the additional load of performing many other tasks. For example
  • Your server or workstation meets the minimum requirements; however, if you have installed other applications that tax the processor, RAM, or hard disks, the minimum requirements will no longer apply
  • Keep in mind the minimum requirements are just the bare minimum. If the server or workstation is performing other tasks, you must have computers that meet or exceed the recommended specifications
  • See 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
• Incorrect workflow used during the Sage 300 server migration
• Incorrect workflow used to delete company folders
• Or the server crashed prior to migration
  • See Slow performance of Sage 300 Construction and Real Estate after migration
• If only one or a few of your reports are affected, the way the report was designed may be the cause (such as how it accesses and sorts the data)
  • Contact the person who originally customized the report for assistance troubleshooting the report design
• 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

[BCB:156:Chat 300 CRE US:ECB]

Issues caused by a large Log Viewer file (QLM)

Sage System Verifier fails on Windows Event Log Sources