Error -1074360311 When Trying to Use My Camera in LabVIEW or LabWindows/CVI

Updated Jul 4, 2023

Reported In


  • PXI Chassis


  • LabVIEW
  • Measurement & Automation Explorer (MAX)


  • NI-IMAQdx

Issue Details

I am trying to acquire images from a camera using the NI-IMAQdx driver, but I receive the following error:

Error 1074360311: Camera Not Found.

In some cases, I can even acquire images on NI MAX or using third party software, but not from LabVIEW or LabWindows/CVI. 


This error occurs when IMAQdx is unable to find a camera with the name that you specified in the Session In input, likely because the camera name changed or is incorrect. Try the following steps to resolve the issue:
  • Make sure that the Session In input of the IMAQdx Open Camera VI is not left blank.
  • Check the name of the camera on NI MAX to make sure that it matches the name on the LabVIEW or LabWindows/CVI code. Alternatively, you can change the name of the camera.
  • Temporarily disable your firewall. If this solves the problem, try adding LabVIEW and NI MAX to the list of firewall exceptions. You may need IT help to disable the firewall or add an exception.
  • If you are using an executable and the camera name is hard-coded in the code with a constant, when the executable is deployed to the target computer, the camera name is likely to be different on the target. This is even true when using the same camera that was used on the development computer because IMAQdx will automatically assign a new name to any new camera that it discovers. By default, IMAQdx cameras are given names starting with cam0 and proceeding to cam1, cam2 and so on. The best way to avoid this issue is designing the executable to allow the user to specify the camera from the front panel by using a control instead of a constant.
  • This error can also occur when you attempt to use a reference to an NI-IMAQ camera with the NI-IMAQdx functions and VIs. Please refer to Does My Camera Use NI-IMAQ, NI-IMAQdx or NI-IMAQ I/O? to use the correct function. 
  • This error can be fixed after reinstalling the drivers and activating them again.