LabVIEW files recovery dialog can cause HDL Workflow Advisor step to error

[jtcalvert]

Description:

In the HDL Workflow Advisor, step 1.2 is the first step to launch LabVIEW. If you were previously using LabVIEW and had the IDE close unexpectedly, or got aborted during a system restart for example, you may get a File Recovery dialog box popup during this step. If you close the file recovery window, you see the front panel of a VI called ServerRunner_CLI.vi open but it doesn't seem to run.

If you continue to wait, or if you close the ServerRunner_CLI VI, step 1.2 in the advisor throws an error:

Steps to reproduce:

1. Do some edits to a LabVIEW VI or project in the IDE to cause a dirty dot.
2. Wait long enough for LabVIEW autosave to run (default is 5 minutes).
3. Abort LabVIEW from Task Manager without saving.
4. Run the Workflow Advisor on your HDL model.
5. When you run step 1.2, you should see the File Recovery dialog pop up when LabVIEW opens.
6. Choose to discard the autosaved files.
7. Observe that ServerRunner_CLI.vi opens and then eventually step 1.2 errors out.

Workaround

After you get the error in Workflow, close LabVIEW completely and run step 1.2 again.

You can also prevent the error from happening by making sure there are no autosaved files in \LVAutoSave directory