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.
DEVELOPER REFERENCE
Look up DQMH framework errors by number, name, or the text you see in LabVIEW.
8 documented errors
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.
The “%s” module is currently running as singleton, but the Start Module VI was called with 'Run as Singleton' specified as FALSE.
%s Module is not running.
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.
%s Module was unable to synchronize events.
Not a single instance of “%s” Module running.
The “%s” module is currently running as cloneable, but the Start Module VI was called with 'Run as Singleton' specified as TRUE.
The request timed out while waiting for a reply. The error message supplies the context.
Message format: %s
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.
No matching error. Try the number alone or a shorter phrase.
Need help with your application?
Find technical support →