The content is shown in another available language. Your browser may include features that can help translate the text.

Causes of "Resetting VI" Message in LabVIEW

Updated May 16, 2018

Reported In

Reported In shows products that are verified to work for the solution described in this article. This solution might also apply to other similar products or applications.

Software

LabVIEW

Programming Language

LabVIEW G

Issue Details

Why do I sometimes get a Resetting VI: (VI name) message when I abort my code in LabVIEW?

Solution

Potential Causes for "Resetting VI: (VI name)" Message in LabVIEW:

- In LabVIEW 5.0 or later, Aborting a VI will cause the user interface thread to send a message to all of the execution threads of a VI to tell them to reset. Instead of immediately terminating the other threads, LabVIEW sends a request that they stop working on their current task. A dialog box is then displayed while the top-level thread waits for all the threads to reset. If the dialog box remains on the screen for longer than a few seconds, one of the threads is most likely busy finishing a task (such as I/O) or is performing a blocking operation.

- In general, you should avoid aborting a VI because the state of a VI cannot be guaranteed when aborted. Instead, the VI should be allowed to complete its execution or a method must be designed to programmatically stop the VI. This will allow you to put the application in a known state and reset any resources (such as files or hardware) that the application may have used.

- If you are using LabVIEW on a Non-Multithreaded operating system, this message can also appear if you use the Stop function. The Stop function is designed primarily for debugging and should be avoided for production code because it behaves as if you clicked the Abort Execution button on the toolbar.

- If the resetting message does not disappear, the VI is most likely performing a blocking operation and will manually need to be aborted. In that case, stop the LabVIEW process via the operating system’s process manager such as Task Manager on Windows. Note that this will close LabVIEW and you may lose all unsaved changes.

- It can also appear when LabVIEW has to wait for all processes to terminate before it shuts down. One work around is to wait longer before closing out of LabVIEW.