Error -314004 When Using Network Streams

Updated Jan 31, 2020

Reported In


  • CompactRIO Controller


  • LabVIEW
  • LabVIEW Application Builder Module
  • LabVIEW Real-Time Module


  • Network Streams

Issue Details

I am trying to set up network streams and encounter Error -314004: Failed to Connect.  How do I resolve this error?


This error occurs when the connection between the network endpoints cannot be established. 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 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.
  • Make sure that you have the latest driver installed. 
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 doing this are located in the Platform Support, Installation and Configuration section of Lossless Communication with Network Streams 
  • Ensure the cRIO's code is running and continuously checking for a connection. 
    • The cRIO's User LED light can be used (if available) as an indicator. 
  • 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, 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.