Why is the MetaDefender Managed File Transfer NEXT service failing to start?
This article applies to all MetaDefender Managed File Transfer (MFT) releases.
Issue:
When MetaDefender Managed File Transfer services are starting up, the NEXT service fails to start. Other services such as web server are up, but attempting to log in to the web management console (e.g. localhost:8010) results in the error message “Account not found”.
In Windows event viewer, the following error is found: A .NET application failed.
Root Cause:
Typically, the MetaDefender Managed File Transfer installer comes bundles with required dependencies such as .NET. However, in some rare cases, the bundled installer might be outdated, causing the dependency check to fail during NEXT service startup.
Remediation Steps:
In the Windows event viewer, click the link after “To install missing framework, download…” to download and install the latest version of .NET 8.0 runtime framework.
If further assistance is required, please submit a Support Ticket with the OPSWAT team.