• Replies 5 replies
  • Subscribers 585 subscribers
  • Views 183 views
  • Users 0 members are here
Options
Related

Anti-Virus blocking execution of Cicode functions

Patrice

Hello all,

We are running CitectSCADA 2016 on a server that is running Cortex XDR anti-virus. We have found that this Anti-Virus software "stalls" the execution of some applications for 30 to 50 seconds before allowing the application to run. For example, when we start the compiler, there is a 40 second delay before the compiling window with the progress bar is displayed. Same thing when we launch de cicode editor, etc. To fix this problem, we have excluded from the anti-virus analysis the Citect\bin directory.

However, we still have some problems. We have a button on each screen that enables us to do a screen capture by calling the WinFile(sFileName) cicode. When we use this button, Citect freezes (we see this because the system clock displayed on top of our Citect page stops refreshing for 40 seconds). This is probably because WinFile is a blocking function. What I think is happening is that the WinFile cicode function is calling a process to capture the screen and copy it to the specified directory but the Anti-Virus is analyzing this process and delaying it's execution. 

What I am having difficulty figuring out is what exactly does the WinFile function execute so that we can exclude it from the anti-virus scan. If we disable the anti-virus, there is no delay so I am certain that this is what is causing this delay. Obviously, our IT department does not want to disable the anti-virus so we have to find exactly which files or directories to exclude from the analysis. 

Any help regarding this would be greatly appreciated.

Patrice Jacob

SCADAlogik inc.

Parents 
  • >We have followed the guidelines for Antivirus exclusions, we are not monitoring the Bin, Data and Trend directories. Are there other folders that we should exclude?

    It depends on your project. If you are constantly reading/writing Citect.ini parameters through Cicode, then you may want to exclude the Config folder which contains that file.  You may also want to exclude the Logs folder since Citect constantly writes to it. If your project reads/writes data in other folders, then you may want to exclude them also.

    Note that it is recommended to do scheduled scans of the Bin folder since it does contain program files, unlike the other data folders. You may be able to set the scan to run at a lower priority to try to avoid affecting runtime performance. One customer I worked with found out that the server's hard drive was running near 100% capacity and when antivirus updates installed each day, it would cause communication timeouts as Citect waited for disk access.

Reply 
  • >We have followed the guidelines for Antivirus exclusions, we are not monitoring the Bin, Data and Trend directories. Are there other folders that we should exclude?

    It depends on your project. If you are constantly reading/writing Citect.ini parameters through Cicode, then you may want to exclude the Config folder which contains that file.  You may also want to exclude the Logs folder since Citect constantly writes to it. If your project reads/writes data in other folders, then you may want to exclude them also.

    Note that it is recommended to do scheduled scans of the Bin folder since it does contain program files, unlike the other data folders. You may be able to set the scan to run at a lower priority to try to avoid affecting runtime performance. One customer I worked with found out that the server's hard drive was running near 100% capacity and when antivirus updates installed each day, it would cause communication timeouts as Citect waited for disk access.

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.