FlexLogger Fails to Launch or Crashes Immediately When Opened

Issue Details

• When FlexLogger is launched it will briefly show its splash screen, but after a few seconds it disappears and nothing happens.
• Every time I try to launch FlexLogger the software begins opening but then crashes immediately. The following error message pops up:

• My FlexLogger application crashes with an access violation error:

Solution

FlexLogger might not launch correctly due to an incorrect installation, user permissions issues or a security software blocking the application from starting correctly. One of the initial steps you can take is to check the Windows Event Viewer for any errors involving FlexLogger, like the ones shown below:

Error 1000 can be reported due to different reasons, including an incorrect installation path, while error 1023 and error 1026 have been seen to be reported due to a security software blocking the application or one of its dependencies, error 1026 could also be related to an issue with the installation or version of.NET Framework. In general, you can try the following troubleshooting steps when FlexLogger is not launching correctly:
 

• Run FlexLogger as administrator. You can right-click the FlexLogger application and select Run as administrator.
• Try temporarily disabling your firewall and antivirus. Some functionalities or files that FlexLogger needs to launch correctly could be disabled by security software. If FlexLogger launches correctly after this, you will need to add the exceptions needed to keep the security software enabled and avoid it affecting FlexLogger.
  • If you are using the Sophos anti-malware software, it has been reported that you might need to apply an Exploit Mitigation exclusion type for certain paths like the following:
    • C:\Program Files\National Instruments\FlexLogger\FlexLogger.exe
    • C:\Program Files\National Instruments\Shared\roco\niroco.exe
  • If you are using SentinelOne as firewall manager, it is suggested to whitelist the following applications:
    • C:\Program Files\National Instruments\FlexLogger\FlexLogger.exe
    • C:\Program Files\National Instruments\FlexLogger\NationalInstruments.IoDataPef.Engine.exe
    • C:\Program Files\National Instruments\FlexLogger\NationalInstruments.UserAccount.Application.exe (for logging in)
    • C:\Program Files\National Instruments\FlexLogger\TDMS File Viewer.exe (for viewing TDMS files in Lite mode)
    • C:\Program Files\National Instruments\DIAdem <Year>\DIAdem.exe (for viewing TDMS files when licensed) - Year may vary by FlexLogger version

• This problem can occur if the FlexLogger.exe application file is installed in a location other than the default installation path. Starting with FlexLogger 2021 R1 that is C:\Program Files\National Instruments\FlexLogger. For older versions of FlexLogger, like 2020 R4 and older the expected path is C:\Program Files\National Instruments\<FlexLogger version>. To fix this:
  • Go to the location called out in the Application Error 1000 message in Event Viewer. You should see FlexLogger.exe located there.
  • Move FlexLogger.exe to its correct directory.
    • For example, in the image above showing Application Error 1000, you can see that the faulting application path is C:\Program Files\National Instruments\LabVIEW 2018\FlexLogger.exe which is not the correct installation path. In this case it should be moved to: C:\Program Files\National Instruments\FlexLogger 2018\.
• If FlexLogger.exe is already placed 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.