Sometimes, during the engines downloading/deployment process, some of them may remain in "failed" or "permanently failed" status.

In this case, you can do the following:

• Make sure your system adheres to our system requirements (check the engine "Third Party Dependencies" section) .

• Go to Inventory → Nodes page and check the Nodes one by one and see if there is any issue displayed on the Issues tab. Resolve the issues displayed. Example of issues:

  • If Data Sanitization is the only engine that is not active, you may have to install .NET framework 4.6 and restart the MetaDefender Core services.

  • If you have a local antivirus product installed, you have to add both the OPSWAT and the resources folders to the exclusions list of that antivirus product and then follow the above steps again.

• Disable and enable each failed engine, one after another on the Inventory → Modules page.

• Try executing an engine clean-up by following this KB.

• Starting mid-April 2020 we are going to gradually release each module with a new compiler, beginning with CDR 5.8 engine.

  • Make sure that VC Redist C++ 2017 is installed on your system in order for the engines to deploy successfully.

  • We recommend installing both the 32bit: https://aka.ms/vs/16/release/vc_redist.x86.exe and the 64bit: https://aka.ms/vs/16/release/vc_redist.x64.exe versions (No downtime required).
    After the dependency install, please disable/re-enable the affected engine and it should deploy successfully (become green)

  • If for some reason you can’t install VC redist C++ 2017 until the release of CDR 5.8, please check the solution by following this CDR KB.

If you have followed all of these steps and your engines are still unusable, please see how to create a support package, login into OPSWAT Portal and open a ticket with us, having the support package attached.

This article applies to MetaDefender Core v4
This article was last updated on 2020-03-27
VM