My LabVIEW Application Uses DataSocket and Does Not Work as an Executable

Issue Details

• My LabVIEW application uses DataSocket communication and executes correctly in the LabVIEW Development Environment. When I build an executable, the DataSocket communication does not work. How do I resolve this?
• I tried to run an executable which has DataSocket communication, but communication failed and the LED at Waveform Chart and Numeric indicators turned red color as follows:

Solution

There are several reasons that can cause a LabVIEW executable using DataSocket communication to not work correctly:

1. NI DataSocket needs to be installed on the system.

• Search the Start menu for DataSocket.
• Open NI Package Manager and search the Installed packages for DataSocket,

• Download the LabVIEW 2017 RTE installer from the LabVIEW Run-Time Engine web page. Note: The 2017 version available on NI Package Manager is SP1 and does not include the DataSocket software. 
• Download and install the LabWindows/CVI Run Time Engine

2. If your LabVIEW application programmatically opens and closes the DataSocket server using DataSocket Server Control VI, it needs to be explicitly included in the built application:

• Navigate to the following location and add the VI to the LabVIEW Project: <LabVIEW 20xx>\vi.lib\platform\dataskt.llb\DataSocket Server Control.vi
• Add the VI to the "Always Include" section of the source files category in the application Build Specification Properties, or the executable will not programmatically open the DataSocket Server.
• If you want your application to close the DataSocket Server programmatically, duplicate DataSocket Server Control VI and change the Operation input to close.

3. Incorrect Windows DCOM settings can prevent an executable from successfully opening a DataSocket connection. Many DCOM connection problems can be overcome by disabling DCOM authentication for your application by adding the following line to the executable's INI file:

ole.AuthnLevel = 1

Additional Information