Skip to content
logo Knowledgebase

How to exclude Sage 100 from antivirus, Real-time scans

Created on  | Last modified on 

Summary

How to exclude Sage 100cloud (Sage 100c, formerly MAS90/MAS200) from antivirus, real-time scans in Sage 100cloud.

Description

This information helps to minimize interference by security programs when working.

Cause

Antivirus software is targeting or interfering with the functionality of a program, system, or data files for Sage 100. Issues include lockups, "error #0" record/file busy errors, error #12 "files doesn’t exist (or already exists)" and slow performance.

Errors during installation of Sage 100 or Sage 100 workstation could mention SY_installationObject, cm_UDTListingWrk.M4T, cm_detailreportwrk.m4t, etc. with file name changing on different attempts.  These occur do to files locked by the antivirus real-time scan.

Resolution

 CAUTION: This solution requires advanced knowledge of Windows security and network settings. Sage isn't responsible for any issues that arise from changes to these settings. Ensure you back up all system and application databases necessary for a complete restoration. It's advisable to contact a certified consultant or your system administrator for assistance.

 

 NOTE: Watch out for antivirus products installed on the physical server hosting a virtualized server running Sage 100. Watch out for firmware-based (or other) antivirus installed on routers, across VPNs, in the cloud.

For Sage Intelligence running workstations, add.SDF file type and local folder to exclusions for workstations. This avoids "Access to the path 'C:\Users\xxxx\AppData\Local\Alchemex (Pty) Ltd\TempFiles\alcworker_638112906898412190.sdf' is denied," when running Sage Intelligence on that workstation.

Consider testing by temporarily disabling your antivirus product to see if this improves performance: speed file locking problems encountered, error messages, etc.

If performance improves, exclude the Sage 100 programs, folders, and file extensions from your Antivirus program:

In your Antivirus product:

  • Disable any aggressive or continuous (also known as on-access, constant, or "network scanning") monitoring or scanning of Sage 100:
    • "..\MAS90\Home\Pvxwin32.exe"
    • "..\MAS90\Home\pvxiosvr.exe"
    • "..\MAS90\Launcher\Launch32.exe"
    • "..\MAS90\Launcher\Launcher.old.exe"
  • Exclude the "..\MAS90" directory and sub-directories and contents on the server where you have Sage 100 installed.
    • Note: Repeat for the workstations, if using Sage 100 Advanced or Premium editions. The default workstation install location is: C:\Sage\Sage 100 Workstation\.
  • On Sage 100cloud workstations, including Standard, there are local folders created for Sage 100: exclude the Crystal Reports install (default: C:\Program Files (x86)\SAP BusinessObjects) and Common Components folder (Sage 100 2019 and earlier = C:\Program Files (x86)\Common Files\Sage. Sage 100 2020 and later = C:\ProgramData\Sage\Common Components).
  • On Sage 100cloud workstations exclude the "Sage 100" folder under the Windows user's Documents folder.
  • Exclude the following path:
    "C:\Users\Windows_Username\AppData\Local\Temp\_autoupdater\," where Windows_Username represents the name of the user's Windows account.
  • Exclude the following file extensions:
    • AUC, DCL, DD, DDE, DDF, EXP, LCK, LIB, KDF, M4D, M4L, M4P, M4T, M4X, PRM, PVC, PVX, RPT, SOA, XEQ
  • Spa.NA.Com must be a trusted site

Note: It’s okay to run nightly scans when users are out. 

Keep in mind settings for exclusion settings take time to sync in multi-tiered environments such as a cloud-based antivirus solution.

 

Need more help?

Chat now