This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

FlexLogger Failed to Connect to the Logging Engine

Updated May 22, 2024

Reported In


  • FlexLogger

Issue Details

I am using FlexLogger 2022 Q2 or older. When I open FlexLogger and create a new project, it takes a long time to load. Eventually, I receive the following error:

FlexLogger failed to connect to the Logging Engine. The erl.exe sub-process run-time is possibly stalled. This issue usually resolves with no additional action required, but may take some time to do so. The issue can also be resolved by ending the erl.exe process in Task Manager.


FlexLogger 2022 Q2 and older versions use the ERLANG/erl.exe process to work properly. This error is related to the erl.exe process being stalled or not running at all on your system.

Firstly, if you can update to FlexLogger 2022 Q4 or newer, then please update, as from 2022 Q4, FlexLogger no longer uses ERLANG/erl.exe. If you cannot update to 2022 Q4 or newer due to any compatibility issues and/or your license restrictions, then please follow the instructions mentioned below.

To resolve this error, you will need to restart the erl.exe process. One way is to manually kill the erl.exe process in your computer's Task Manager and then restart FlexLogger, which should normally restart the erl.exe process. To do that, perform the following steps:
  1. Open up Task Manager by right-clicking on your Taskbar and selecting Task Manager or by pressing the shortcut key Ctrl + Alt + Delete.
    • If you are on Windows 10, select the More Details button in the Task Manager window to view a detailed process list.
  2. Navigate to the Details tab of Task Manager. 
  3. Select the erl.exe process and then click End Task.
  4. Restart FlexLogger.
If you do not see an erl.exe process in Task Manager, then it has completely stopped running on your system. One way to start the erl.exe process is to start/restart the NI SystemLink Message Bus service on your system from the Windows Service Manager. To do that, perform the following steps:
  1. Close FlexLogger.
  2. Open the Windows Service Manager. To do that on Windows 10, perform the following steps:
    1. Right-click on the Windows Start button to open the WinX menu.
    2. Select Run.
    3. Type "service.msc" in the Run window that opens.
    4. Windows Service Manager will be opened.
  3. Find the NI SystemLink Message Bus service and click Start or Restart, depending on whether the service is already running or not.
  4. Now, check in the Task Manager if the erl.exe processes have been started or not.
  5. If yes, then restart FlexLogger.
If you do not have the NI SystemLink Message Bus service in the Windows Service Manager, or if you still continue to see this error message, then try the following steps:
  • Repair FlexLogger by following the instructions provided in Repair Software In NI Package Manager (NIPM).
  • Fully uninstall and reinstall FlexLogger.
  • Try updating and installing a newer version of FlexLogger, even if it is older than 2022 Q4. For example, if you are seeing the issue in FlexLogger 2020, try updating to 2021.