FlexLogger Fails to Launch or Crashes Immediately When Opened

Updated Jun 3, 2020

Reported In

Software

  • FlexLogger 2019 R4

Issue Details

I have installed FlexLogger and want to use the software now. But every time I try to launch FlexLogger the software either never opens or it starts opening, then crashes immediately and the following error-message pops up:

FlexLogger has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.


In the Windows Event-Log I see two errors with the ID 1000 (Application Error) and 1026 (.NET Runtime Error):





What can I do in order to make FlexLogger running properly?

Solution

  • This problem can occur if the FlexLogger.exe application file is installed in a location other than C:\Program Files\National Instruments\[FlexLogger version]. For example, in the image above showing Application Error 1000, you can see in the error message that the Faulting application path is C:\Program Files\National Instruments\LabVIEW 2018\FlexLogger.exe which is not the correct installation path. If this is true in your case:
    1. Go to the location called out in the Application Error 1000 message in Event Viewer. You should see that FlexLogger.exe is located there.
    2. Move FlexLogger.exe to its correct directory: C:\Program Files\National Instruments\[FlexLogger version]. For example, if you are using FlexLogger 2020 R2, then the FlexLogger.exe file should be moved to C:\Program Files\National Instruments\FlexLogger 2020 R2\.
  • If FlexLogger.exe is already located in the correct location, perform a repair of FlexLogger via the NI Package Manager or remove and reinstall the software on your PC to make sure that the software is installed without errors.
  • The Windows error 1026 could also point to an issue with the .NET Framework. Make sure to have the correct version of the .NET Framework installed, as stated in the Readme for you version of FlexLogger.

Additional Information

The error 1000 also points to the KERNELBASE.dll. There are some instructions online how to fix KERNELBASE.dll errors, but it is recommended to perform the above mentioned steps before working with this dll in the System32 folder, because many forums discussions mention, that this troubleshooting steps do not improve the situation.