DQMH / SEARCH

DEVELOPER REFERENCE

Find the error. Understand the message.

Look up DQMH framework errors by number, name, or the text you see in LabVIEW.

DQMH’s allocated error range is 403680–403719, starting with DQMH 4.0. The entries below describe the documented codes in that range.

%s represents text supplied at runtime.

403680

Cannot run as clone

The “%s” module is currently running as singleton, but the Start Module VI was called with 'Run as Singleton' specified as FALSE.

403681

Module Not Running

%s Module is not running.

403682

Module Not Stopped

The Stop Module VI for the %s module timed out while waiting for the module main VI to stop. The module main VI may still be running.

403683

Module Not Synced

%s Module was unable to synchronize events.

403684

Module Not Running

Not a single instance of “%s” Module running.

403685

Cannot run as singleton

The “%s” module is currently running as cloneable, but the Start Module VI was called with 'Run as Singleton' specified as TRUE.

403686

Request and Wait for Reply Timeout

The request timed out while waiting for a reply. The error message supplies the context.

Message format: %s

403687

Cannot run as singleton

The “%s” module cannot be run as singleton because the Master Reference is still open from a prior run as cloneable. If you plan on running this module as both singleton and cloneable, consider changing your Main VI to wire a value of TRUE to the 'Close Master Reference' input of Init Module.vi.

Need help with your application?

Find technical support →