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 Nov 8, 2019

Reported In

Software

  • FlexLogger

Issue Details

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.
 

Solution

To resolve this error, you will need to end the erl.exe process in your computer's Task Manager, and then restart FlexLogger. 
  • Open up Task Manager by pressing Ctrl + Alt + Delete
    • ​If you are on Windows 10, select More Details to view a detailed process list.
  • Navigate to the Details tab of Task Manager. 
  • Select the erl.exe process and then click End Task.
  • Restart FlexLogger.

If you continue to see this message, try to repair FlexLogger following the indications provided in Repair Software In NI Package Manager (NIPM).

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement may be required, and support options vary by country.