Optimising Sage 300 & CRM: Role of Antivirus Exclusions

When implementing Sage 300 and Sage CRM, one of the most frequently overlooked configurations that can make a significant impact on performance is the setup of antivirus and threat protection on the server environment. Without the right exclusions in place, antivirus software can constantly scan Sage applications, resulting in sluggish performance, frequent crashes, and untraceable errors.

In this article, we’ll discuss the specific configurations needed to prevent antivirus interference with Sage 300 and Sage CRM, and why implementing these steps is essential for a smoother, more reliable user experience.

Understanding the Impact of Antivirus on Sage 300 and Sage CRM

Antivirus software, while essential for security, often uses real-time scanning to monitor files and applications for potential threats. However, with Sage 300 and Sage CRM, this constant scanning can slow down these applications considerably, as the antivirus treats each Sage operation as a new event to scan. This not only impacts speed but can lead to crashes and unexplained errors that disrupt productivity.

By configuring antivirus settings with specific exclusions for Sage 300, Sage CRM, and related applications, you can significantly improve performance and stability.

Setting Up Antivirus Exclusions for Sage 300 and Sage CRM

Below is a detailed breakdown of the essential antivirus exclusions needed for optimal performance:

1. Exclusions for the Sage 300 Server

To avoid unnecessary scanning and delays on the Sage 300 server, add exclusions for the following:

• Sage 300 Installation Folder Paths: Exclude the main Sage300 directory to prevent real-time scanning of core files.
• “Common Files” Directory: This folder, located within Program Files (x86), contains essential shared files for Sage applications. Add exclusions here to avoid performance issues with Sage’s services.
• Sage Services Application Folders: These folders often contain executable (.exe) files that perform critical functions. Ensure that exclusions are applied not only to the folders themselves but also to each executable file within these folders.

2. Additional Exclusions for 3rd-Party Add-Ons

If you use add-ons like Sage Intelligence Reporter and Visual Basic Macros, it’s necessary to exclude specific Microsoft Excel components:

• Microsoft Excel Installation Folder: Exclude this folder, as Sage Intelligence Reporter often works directly with Excel for data analysis and reporting.
• Excel Executable Files: To prevent delays and crashes when running reports, add exclusions for excel.exe and related executables within the Excel installation path.

3. Terminal Server Considerations

For businesses using Sage 300 on a terminal server, additional exclusions are needed:

• Network Folder Paths: If workstations access Sage 300 through a network path, exclude the network folders where the workstation setup for Sage 300 resides.
• Locally Installed “Common Files” Folder: Similar to the server, add exclusions to the locally installed “Common Files” folder on the terminal server to avoid delays.

4. Exclusions for Sage CRM Integration with Sage 300

When Sage CRM is integrated with Sage 300, we’ve observed significant performance improvements across environments by applying the following:

• Sage CRM Installation Path: Exclude the main Sage CRM directory to reduce scanning delays.
• Executable Files: Just like with Sage 300, excluding the .exe files within Sage CRM’s directories will prevent interference from the antivirus and enhance system speed and reliability.
• Sage CRM and Sage 300 Integration Points: Apply exclusions for any specific integration paths or files that connect Sage CRM to Sage 300, especially if they interact frequently to sync data.

Conclusion

Configuring antivirus exclusions for Sage 300 and Sage CRM is a simple yet powerful way to optimise application performance and prevent system disruptions. By excluding key directories and executable files, you can minimise unnecessary scanning and allow Sage applications to run smoothly. This approach has consistently led to faster load times, fewer errors, and a vastly improved user experience across our client environments.

If you’re experiencing sluggish performance or unexplained errors in Sage 300 or Sage CRM, revisiting your antivirus settings may be the solution. For guidance on implementing these configurations, please don’t hesitate to reach out to our support team.

‍