Toggling FSD server alarm from ACT to RTN every milliseconds-xA6.0.3.2
Hi,
We are getting continuous toggling alarm every milliseconds from FSD server.
Description of Alarm: File Set Distribution_basic_CPRIASCS File system error(1) on system alarms Event detail:A file system operation failed. Error while renaming File/directory c:\OperatieITdata1\fsdserver\data\d012\d111
system running: xA6.0.3.2
Please let us know if we load PLC Connect Ru4 and xA6.0.3 Ru5 may fix the issue as release notes telling:overwrite of FSD server will be corrected.
Answers
0
As I recall, "Error while renaming" errors are typically due to lack of exclusion from McAfee AntiVirus on-access scanning.
The way we spot this is by installing procmon.exe from www.sysinternals.com and record/view activity on the FSD folder and subfolders (filter for this folder only, e.g. \OperateITData\FsdServer). If you see McAfee or any other antivirus-executable working with the FSD files, you likely have an issue with exclusion of on-access scanning.
We have had a handful of support cases where the caller had to uninstall and reinstall McAfee + make new configuration of files/folders excluded from on-access scanning. But please verify your active exclusions first; sometimes a letter become typed wrong or the Include Subfolders option were not ticked, etc. Ultimately, remove McAfee, verify success, then reinstall McAfee + apply exclusions once more.
The way we spot this is by installing procmon.exe from www.sysinternals.com and record/view activity on the FSD folder and subfolders (filter for this folder only, e.g. \OperateITData\FsdServer). If you see McAfee or any other antivirus-executable working with the FSD files, you likely have an issue with exclusion of on-access scanning.
We have had a handful of support cases where the caller had to uninstall and reinstall McAfee + make new configuration of files/folders excluded from on-access scanning. But please verify your active exclusions first; sometimes a letter become typed wrong or the Include Subfolders option were not ticked, etc. Ultimately, remove McAfee, verify success, then reinstall McAfee + apply exclusions once more.
Add new comment