Views:

This usually occurs because of the sharing violation wherein the agent accesses the file/process and then another application attempts to open the same file/process.

A common issue is that O365 apps cannot be saved due to file permission errors or file is in use by another application or user.

To address the issue, do the following to defer the scanning of the agent:

  1. On the WFBS Server, navigate to <WFBS Server Installation folder>\PCCSRV.
  2. Open ofcscan.ini using a text editor.
  3. Add the following lines in the [TrendX_Settings] section of ofcscan.ini:
    DS_ProcessCount=x
    DS_ProcessName000=process1.exe
    DS_ProcessName001=process2.exe

    where x = number of processes that you want to add to the defer scan list

    For example:

    DS_ProcessCount=52
    DS_ProcessName051=EXCEL.exe
  4. Save the file.
  5. Log on to the WFBS web console.
  6. Go to Administration > Global Settings and click Save at the bottom.
  7. Manually update the affected WFBS agent.
  8. Check the TXS.ini in the WFBS agent folder, and it should contain the following settings. 
        [TrendX_Settings]
    ExceptionCount=0
    DS_ProcessCount=52
    ...
    DS_ProcessName051=!CRYPTEX7CE259E5AA8B6E3D3FE12D60C52335CA04245384D961652A044E9F83698C8B32DA9DAE40431F842AA9BCAF0FBAA0E6FCE69B2549420EF388DF99977A1446EA62FF5BA86B87CF3A62555ACA0BABB4E718
     
    This is an example file, so the encrypted string will be different. This file should not be edited manually.
     

  1. On the Apex One Server, navigate to \PCCSRV.
  2. Open ofcscan.ini using text editor.
  3. Add the following lines in the [Global Setting] section of ofcscan.ini:
    DS_ProcessCount=x
    DS_ProcessName000=process1.exe
    DS_ProcessName001=process2.exe

    where x = number of processes that you want to add to the defer scan list

    For example:

    DS_ProcessCount=1
    DS_ProcessName000=EXCEL.exe
  4. Save the file.
  5. Log on to the Apex One web console.
  6. Go to Agents > Agent Global Settings and click Save at the bottom.
  7. Manually update the affected Apex One agent.
  8. Check the TXS.ini in the Apex One agent folder, and it should contain the following settings. 
        [TrendX_Settings]
    ExceptionCount=0
    DS_ProcessCount=1
    DS_ProcessName000=!CRYPTEX!DBBCD5023E9DD0DEC00C749478DFD07C
    DS_ProcessName001=!CRYPTEX7CE259E5AA8B6E3D3FE12D60C52335CA04245384D961652A044E9F83698C8B32DA9DAE404
     
    This is an example file, so the encrypted string will be different. This file should not be edited manually.
     

Please contact Trend Micro Technical Support for further assistance.