Call Chain Error occured during EXE Creation

Question

When I am trying to create EXE then while generating preview the following error pops up. I have mass compiled the office vi s in the vi.lib but still the problem is occuring. Can anybody solve this problem?
"Unable to generate preview. An included VI or one of its dependencies does not exist. Open all 
Startup/Exported/Dynamically called VIs, recompile them  (Ctrl-Shift Click the run arrow), and save them to
update their dependencies.
D:\Applications\IISU Vibration and Order Analysis\Source Code\BTS_Client\BTClnt_Main\BETS Splash Screen.vi
<Call Chain>Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to
Disk Hier.vi -> ABAPI Get Settings From File.vi -> EBEP_Invoke_Build_Engine_Preview.vi ->
EBUIP_Build_Rule_Editor.vi -> EBUIP_CreateNewWizard_Invoke.vi ->
EBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly
formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on
Linux."
NI-488:  Non-existent board.

Answer 1

Hi IQ,
Welcome to the forums!
This error is usually found (as the error suggests) when a subVI or a support file (DLL, custom control, etc) isn't able to be found by the application builder.  Possible reasons for this could include subVI's no longer located in their original paths and need to be relinked, a DLL that isn't included in the build, and many other possibilities.  The VI in question for this case is BETS Splash Screen.vi , though the exact reason why this is happening is not possible to determine from just the error description, so more information is needed.  Can you run the program as a VI?  Does BETS Splash Screen.vi have a solid run arrow?  What version of LabVIEW are you using?  If you mass compile your project VI's does this clear the problem?
Cheers,
Matt Pollock
National Instruments