Trouble using LabVIEWCLI

[Oli_Wachno]

Hi there,

I started playing a bit with LabVIEW CLI 1.1 but have failed miserably so far 

Starting small, I thought just to have a short pipecleaner masscompiling a directory

LabVIEWCLI -Verbosity Diagnostic -LabVIEWPath "C:\Program Files (x86)\National Instruments\LabVIEW 2017\LabVIEW.exe" -PortNumber 3364 -OperationName MassCompile -DirectoryToCompile "C:\Test"

LabVIEW launches, but CLI returns with an error. The diagnostic file holds the following information

Using LabVIEW: "C:\Program Files (x86)\National Instruments\LabVIEW 2017\LabVIEW.exe"
LabVIEW launched successfully.
Error code : -350000
Error message : LabVIEW CLI: (Hex 0xFFFAA8D0) The CLI for LabVIEW failed to establish a connection with LabVIEW. Ensure LabVIEW is running with VI server enabled on the correct port number. To enable VI server in LabVIEW, select "Tools>>Options>>VI Server" and enable the "TCP/IP" checkbox. If the port number under "TCP/IP" is not 3363, you must specify the port number using the "-PortNumber" argument.
An error occurred while running the LabVIEW CLI.

VI Server seems configured correctly

So I thought, I'd try changing the VI Server Port to 3364, just to try

Same thing happens:

LabVIEW launches, an error is reported on the command line, LabVIEW stays open.

To check if VI Server is working correctly, I have used VI Package Manager to verify the connection. This works fine.

Any ideas?

Cheers

Oli

[StefanLemmens]

Make sure the Machine Access List allows access for 127.0.0.1, this is necessary to allow the communication between the LabVIEW-CLI and VI Server.

Best Regards,

Stefan Lemmens

Intersoft Electronics

[Oli_Wachno]

---

@StefanLemmens wrote:

Make sure the Machine Access List allows access for 127.0.0.1, this is necessary to allow the communication between the LabVIEW-CLI and VI Server.

Best Regards,

Stefan Lemmens

Intersoft Electronics

---

Thanks for the tip. Added 127.0.0.1 explicitely yet it does not help in this case.

[StefanLemmens]

Another problem might be that the LabVIEW CLI won't start VI Server fast enough.

You can find more info here.

I got it to work with these settings:

AppExitTimeout = 10000
OpenAppReferenceTimeoutInSecond = 30.000000
AfterLaunchOpenAppReferenceTimeoutInSecond = 90.000000

Due to this we switched from using the LabVIEW-CLI to G-CLI

Best Regards,

Stefan Lemmens

Intersoft Electronics

[Oli_Wachno]

Ok.... so I raised the time-outs as described. Error remains.

I shall try on a different computer outside the corporate enviroment... maybe there is some strange group policy which keeps this from working. Wouldn't be for the first time....

Thanks for the input!

Oli

[StefanLemmens]

Just noticed in your screenshot that the portnumber (3363) doesn't match the one in your command line (3364).

Best Regards,

Stefan Lemmens

Intersoft Electronics

[Oli_Wachno]

---

@StefanLemmens wrote:

Just noticed in your screenshot that the portnumber (3363) doesn't match the one in your command line (3364).

Best Regards,

Stefan Lemmens

Intersoft Electronics

---

Hi Stefan,

you're right. The code and the screen shot don't match: took the screen shot while experimenting.

BTW: tried at home last night on a VM with LV2018: worked smoothly. Next step will be to set up a VM with LV2017 and check again.

Cheers

Oli

[StefanLemmens]

Hi Oli,

how smooth is "smoothly"?

I still have a very long delay (more then 30sec) between running the command and LabVIEW actually doing something.

Best Regards,

Stefan Lemmens

Intersoft Electronics

[Oli_Wachno]

Hi Stefan,

smooth as in it is working on that particular VM using the standard parameters of the CLI INI file.

But: this is a LabVIEW only installation. No toolkits like RT or FPGA installed.

But speaking of slow spinup.... I remember having had troubles with an old version of the SVN Toolkit when opening large projects. Don't know if this is still the case.

BR

Oli

[Sam_Sharp]

Did you download the CLI from the web? Do you need to 'unblock' it in the exe properties?

Of course, it may be that you need to unblock the executable on your firewall...your IT policy might only allow signed/whitelisted executables to have network access on certain ports.