Error -314350 When Using Network Streams in LabVIEW

Updated Apr 17, 2026

Reported In

Software

  • LabVIEW

Issue Details

I'm trying to connect a Network Streams writer endpoint to an existing reader endpoint in LabVIEW, but I get the following error:

Error -314350 occurred at <name>.vi

Possible reason(s):

LabVIEW: Another application is already streaming data to an endpoint in the context you specified. If you specified a context name in the reader name or write name terminal of the endpoint, you must specify an unused context name. If you did not specify a context name, you must specify an unused context name by entering an endpoint URL in the reader name or write name terminal.
 

Solution

This error occurs when connecting to a reader endpoint that is orphaned and in a bad state. This could happen if any of the following situations occurred:

  • A writer and a reader are created and linked.
  • The writer is destroyed, leaving the reader orphaned.
  • A new writer is created and attempts to connect to the existing reader.
  • The below mentioned NI services are not or partially running.

 

To avoid issues while using Network Streams, be sure to follow these considerations:

  • Ensure the the following NI services are running on your host:
  • Make sure that firewalls and antivirus are turned off or configured to allow NI hardware and software exceptions.
  • There are also some recommendations for firewall settings specific to network streams.
  • Make sure the endpoints for the network streams are specified correctly.
  • If there are any Group Policy Objects configured, turn them off to test the Network Streams.
  • Make sure that NI Installer is not running or installing anything else at that time. If it is running in the background, or if the installation was paused, cancel the installation or let it finish and then reboot the computer.

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.