What to do if Core and PostgreSQL Services are no longer starting after force restart of ometascan service ( Error Code 610 )

In specific situations, it might be necessary to restart the MetaDefender Core’s main service ( ometascan ) so that specific changes and/or updates can take place (changing the log level, configuring registry keys and so on… )

However, if any scan was in progress at the time the service was restarted, or the Core does not successfully clean some residual files, this might lead to an issue where the service will no longer start, and both the Event Viewer of the Windows and the Core Logs will point to the same issue:

In that situation, it might be necessary to delete the resources folder of MetaDefender Core, that can be found under the following path.

This will help by the fact that the residual/corrupted files are manually deleted and MetaDefender Core will no longer need to associate them to anything, allowing the service to successfully start.

*NOTE: If the This will help by the fact that the residual/corrupted files are manually deleted and MetaDefender Core will no longer need to associate them to anything, allowing the service to successfully start.

NOTE: If the *tempdirectory** registry key was configured, a resources folder will also be generated under the specified path, and this will need to be cleared as well.