LabVIEWCLI error 1130

[ChristopherDale]

Hi amritnagi,

I had a chance to look more closely at the GitHub repo you pointed us to. I'm not 100% sure this is the same project as what the OP and I are talking about. We are talking about the LabVIEWCLI.exe application available @ https://www.ni.com/en/support/downloads/software-products/download.ni-labview-command-line-interface.... From what I can see in the C# code available on GitHub that is a different project. If you look at the command line switches available for in the GitHub repository, they are different; also, the executable name is different in the GitHub repository as well (ex. labview-cli vs. LabVIEWCLI.exe).

Could you confirm the repository you pointed us to is actually the same thing as the link I supplied above? My guess is that they misunderstood and pointed you in the direction of Wiresmith design's CLI which is sort of a different beast. https://forums.ni.com/t5/Reference-Design-Content/Wiresmith-Technology-LabVIEW-Command-Line-Interfac.... Tricky since they are both called LabVIEWCLI 😄

[aptivo]

For service pack 1 of LabVIEW 2018 there is also no bugfix for this CAR#

https://www.ni.com/pdf/manuals/374715k_0113.html

[nathan-p2]

So I ran into this error as well, but for my situation I think the cause is different.  I get this error when I try to run the labview cli interface, and the project DOES have broken VIs.  In our project, we added a vi package dependency, but it didn't get added to our build server, and whenever the build server tried running it would respond with this error.  Not a very clear or direct error for our cause, but when I installed the missing dependency, and fixed all the broken VIs in the project, it was able to work again.

Figured I'd share this in case it'll help someone else.  Good luck!

[petrz]

The error 1130 happens because LV (VI server?) stops responding to CLI client. This may happen during loading or building of project. My guess is in your case the broken project took lot of time to load, so the connection was lost before you get the error.

If anyone want to seriously use continuous integration or automate building with LabVIEW, forget about using CLI shipped with LV - it's useless, you will run in this problem soon or later as your project grows. You can try the CLI from github (it looks like it may work, since it uses TCP/IP instead of VI server) or write your own - this give you the best control.

[aptivo]

For my case it is caused by the loading time. The project itself is correctly building on the build machine. But if trying to use the CLI I run into described error. Was only a try so I am still using a LabVIEW vi with command line arguments which works fine for my case.

[pawhan11]

I have tried to use Build.vi and it works without problems. 

But sometimes build fails for no reason is another mistery. When I try build up to 5 times it will eventually pass 🙂