It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda MSP Knowledgebase

'Application cannot be started' error when launching Remote Control

  • Last updated on

The following article can be used for not only the screenshot as seen below but also to troubleshoot any possible failed connections use Remote Desktop launched from your Service Center UI in Barracuda RMM.

clipboard_ecd1322333bc8b2c402e074f3ba5a667c.png

Method 1


Reinstall the Meta4 ClickOnce extension in Chrome, Firefox or Microsoft Edge (based on Chromium) extension. This is required by Barracuda RMM to utilize RDP sessions, but the extension itself is not supported through the Barracuda RMM support team.

clipboard_e5e8ebb2d62afd04bdb6343a8b8ec9fe3.png

Google Chrome
  1. Click the Hamburger Menu the top right.
  2. Select Settings.
  3. Select Extensions.
  4. Remove the Meta4 ClickOnce Launcher.
  5. Reinstall from the Chrome Store.
Mozilla Firefox
  1. Click the Hamburger Menu the top right.
  2. Select Add-ons.
  3. Select Extensions.
  4. Remove the Meta4 ClickOnce Launcher.
  5. Reinstall from the Firefox Extension Store.
    1. Note: Support recommends using Breez ClickOnce for Firefox found here
Microsoft Edge (based on Chromium)
  1. Click the Hamburger Menu the top right.
  2. Select Extensions.
  3. Remove the Meta4 ClickOnce Launcher.
  4. Reinstall from the Chrome Store.
    • Must allow extensions from other stores.

Method 2


In an admin-level command prompt run the following command to clear the ClickOnce application cache:  rundll32 dfshim CleanOnlineAppCache

Method 3


In an admin-level command prompt run the following command to rename the ClickOnce plugin cache:  ren %localappdata%\Apps\2.0 2.0.old

Method 4


  1. On the computer initiating the Remote Control connection, browse to the following folder: C:\Users\{USERNAME}\AppData\Local\Apps
  2. Delete, move, or rename the 2.0 folder.
  3. Once the 2.0 folder has been deleted, moved, or renamed, refresh the web browser with the service center dashboard and launch the connection again.

Logs Support will like to see


If you are not able to connect still, our support team will want to see specific logs from both the Onsite Manager and the Technician's system. Please follow these logs

  • Tech System: 
    • MWRemoteAccess logs from %LocalAppData% (eg. C:\Users\tim\AppData\Local)
  • Onsite Manager: 
    • OMNetworkServiceTrace logs from C:\Program Files (x86)\Level Platforms\Onsite Manager\Logs
Last updated on