What Are Some Common VI Server Errors? - National Instruments

What Are Some Common VI Server Errors? - National Instruments:

What Are Some Common VI Server Errors? Primary Software: LabVIEW Development Systems>>LabVIEW Full Development System Primary Software Version: 7.1 Primary Software Fixed Version: N/A Secondary Software: N/A Problem: What are some of the common VI Server errors, and what do I need to do to resolve them? Solution: Error 1000: The VI is not in a state compatible with this operation The state of a VI reflects whether the VI is reserved for running. When a VI is reserved for running (or is running), you cannot edit it. Make Current Values Default is an example of a method that edits a VI because it actually changes the composition of the VI. Set Control Value is an example of a method that does not edit the VI because the VI itself does not change when a control value changes. All strictly-typed references reserve the VI for running. Therefore, anytime you use a Call By Reference Node, the VI is reserved for running. You must close this reference before you can edit the VI. Otherwise, you will receive error 1000.VI class references do not reserve the VI for running. You can edit the VI in this case as long as the VI is not actually running. You also can open both a strictly-typed and a VI reference to the same VI, but the use of editing methods and properties is subject to the conditions above. A VI cannot be part of any currently running VI hierarchy if you want to edit it. If the VI is part of the hierarchy, this situation is identical to trying to edit the higher-level VIs with the Invoke Node, which always fails with error 1000. This is because the VI is reserved for running by being part of a running hierarchy. Error 1000 can also occur if you attempt to abort a VI that is in the incorrect execution state, either due to the VI running or being part of another VI hierarchy. Error 66: The network connection was closed by the peer The network connection might have been closed by someone, or LabVIEW is not configured to allow you to be a client. In the second case, you must configure the VI Server to give you the appropriate permissions by selecting Tools»Options (or Edit»Preferences in LabVIEW 5.x). Error 1044: The VI is locked When running as a standalone application, a Property Node in the VI might return error 1044, which causes the called VI not to be opened and the application to run incorrectly. However, the application runs correctly in the development environment. You might experience this warning with various different properties, such as Front Panel Window:Auto Center. To avoid the error, you must set these properties in the VI before building an application. Setting properties like this is considered editing the VI, and editing VIs is not allowed when the VI is built into an application. Error 1043: Feature not supported in this application This error can occur when you use an Invoke Node and the Save Instrument method (or another similar function) in an application. When the application is running, it returns error 1043 and it does not save or perform the specified function. This is because the application is a run-only system; no VI editing is allowed. Because no editing is allowed, you cannot perform actions like saving. Error 7: LabVIEW File not found This error can occur when the specified file path is not correct. Double-check the path you entered. Make sure you are using \ instead of /, make sure you spelled the directory names correctly, and so on. The path must be in the same format as the operating system on which you run the VI. For example, if the path on Windows is c:\windows\desktop\time.vi, the path on UNIX is/c/windows/desktop/time.vi. Error 1003 : LabVIEW VI is not Executable This error can occur when the VI cannot locate its subVI's in the the location they were when the VI was developed.  Typically this happens when a VI is called from an executable on a machine with just the LabVIEW Run-Time engine installed, but it can happen on any machine that doesn't have all of the subVI's in the exact directory structure as the development machine.  Note: If you encounter a VI Server error not described in this document or anywhere else in the KnowledgeBase, please submit the error number in the feedback form below. Related Links: KnowledgeBase 28PCDAB5: Error 63 When Using VI Server to Launch a VI on a Remote Machine KnowledgeBase 268B8SXQ: Error 1003 When Using VI Server in a LabVIEW Application KnowledgeBase 1HSEC18U: Why Do I Get Error 1032: VI Server Access Denied When Using the All VIs In Memory Property? KnowledgeBase 2QEGGE8O: Why Do I Get Error 1000 When Attempting to Abort a VI Through VI Server? KnowledgeBase 50A980BQ: How Can I Call a VI Dynamically From an Exectuable Without Including those VI's in the Build? Attachments: Report Date: 04/19/2001 Last Updated: 09/12/2012 Document ID: 28IAHMDM Your Feedback!  Poor  |  Excellent    Yes No  Document Quality?   Answered Your Question?    1 2 3 4 5 Please Contact NI for all product and support inquiries.

 

'via Blog this'