Intermittent PSQL #85, Environment #48, or Muscle/Basic #0 Errors in AeOpenRelativeFile

Set the Anti-Virus software to not scan PSQL data files. Consult your Anti-Virus software manual for instructions on how to exclude files.

Error Details:
ERROR OCCURRED IN PROGRAM AeData
ERROR NUMBER: MUSCLE/BASIC #0 (AeData:clsAeData:AeOpenRelativeFile)
ERROR MESSAGE:
INFORMATION: \\server\apps\AGRIS\datasets\001\AB~2007071734005000.tmp
RECOMMENDATION: Call AGRIS Customer Support, (800) 366-2474

A PSQL #85 or Muscle/Basic #0 error occurs when the file is closed because Anti-Virus software opens and locks the file to scan causing the next database operation to fail.

NOTE: This error could also be caused by a backup process such as Carbonite that might be actively trying to backup a file when AGRIS/PSQL is actively trying to delete the file. Really any program/service/process that would be trying to interact with AGRIS files in real-time could trigger this kind of error. Such processes or services should be scheduled so they can take place when users aren't actively using the AGRIS system. The error more or less indicates we weren't able to interact (i.e. create, open, update, close, delete) with a temporary AGRIS file in the expected manner.

NOTE: ISSUE CAN IMPACT MSSQL ENVIRONMENTS AS WELL. This is because PSQL database files are not the only files that can be impacted by real-time scanning. Temporary files (AB~*.*), import files and even non-AGRIS files, such as scanned documents that will be uploaded to AttachToo, can experience related issues. Related error messages include:
--Access is denied
--Basic #57 - The process cannot access the file '\\......' because it is being used by another process.

Microsoft Defender for Endpoint (previously known as Windows Defender Advanced Threat Protection or Microsoft Defender Advanced Threat Protection)

Microsoft Defender for Endpoint has been found to cause these errors and defining exclusions can be a bit difficult.

To allow the AGRIS application access without offboarding the machine from Microsoft Defender for Endpoint, create an Allow Indicator for the Hash Value of the application in the MDE portal which is also the strongest type of exclusion you can define in Microsoft Defender for Endpoint. For creating an allow indicator in MDE for the AGRIS executables, follow the below steps.

The Hash Values for AGRIS sysmenu.exe and agris.sys.menu.exe are as follows:
SHA256 Hash Value for sysmenu.exe: F6A257CDB7A211667A995ED71E7057E782D36A953524D5A0300636EE72B7D333
SHA256 Hash Value for agris.sys.menu.exe: 812026E7387762706F94DCAF9480B5E98F0DDE9E022C9DB8AE3782CA86556AF5
SHA1 Hash Value for sysmenu.exe: 3FFA1A1FBDC0DC91899C3F31D8D4FDDF00A2CE9F
SHA1 Hash Value for agris.sys.menu.exe: 7C4A177DC7F0EE13AC059E7A82496CE111A8BB5F

If you wish to verify these Hash Values are correct you can confirm the Hash Values (shown in green below) for sysmenu.exe and agris.sys.menu.exe for both SHA256 and SHA1 by running the following PowerShell commands (shown in yellow below) from the Command Prompt. Adjust the path to the sysmenu.exe and agris.sys.menu.exe files as necessary as pertains to the location of your AGRIS installation.
After collecting the Hash Values, login to the MDE portal with global admin credentials.
Navigate to Settings > Endpoints > Rules > Indicators > Add new indicator > File Hash indicator > Enter the first Hash Value in the column and select allow.
Do the same as step 3 for the remaining Hash Values. NOTE: After creating an Allow Indicator, it might take 24 hrs to replicate the change within your system environment.