Solution
Typically, this error occurs when the connection between the network endpoints cannot be established.
If you are just setting this up between to computers or directly on the host machine, then try the following:
- Make sure you have an established connection between the two machines that are trying to communicate. Test this by pinging one machine from the other.
- Make sure the ping times are within the acceptable range and do not reach high values.
- Make sure Network Stream Endpoint configurations and naming conventions are properly set up in the LabVIEW code.
- If multiple instances of an application are generated, each network stream must have a unique context name.
- Disable appropriate firewall and antivirus protection to accommodate LabVIEW networking.
- Try running the LabVIEW Prebuilt Example for creating a Network Stream, listed as Simple Network Streams.lvproj in the LabVIEW Example Finder
- If the issue persists try increasing the timeout time
- Check if the ports TCP 2343, UDP 6000-6010, TCP 59112 are open
If you are using a CompactRIO (cRIO) as one of the endpoints of the Network Stream, note the following recommendations:
- Make sure that the Networks Stream are installed on the cRIO. Steps on what is necessary for installation, and how to properly install this software to the cRIO can be found in this article on troubleshooting the connection between the cRIO and the Host machine.
- Ensure the cRIO's code is running and continuously checking for a connection.
- Reference the LabVIEW FPGA Control on CompactRIO project template to see how the Real-Time code is implemented on the cRIO. Note: You must generate a configuration file to prevent this error from occurring using the Utility - Configuration File Generator.vi, following the instructions on the front panel when using this template.
If this error comes up when you are running an application (executable) but it runs fine when you run it from the development environment there are other considerations to take into account.
- When you are running an application, the security settings for this new executable could be different. If LabVIEW has certain security settings, the executable created by LabVIEW might not have the same settings.
- If LabVIEW was added as an exception on the firewall or antivirus security, make sure the application built by LabVIEW is also added to these exceptions.
- Try increasing the endpoints' creator's timeout as the timing might change from the development environment to the application.