From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Reference

Hi all,

i do Application Reference & Open Application with the following inputs:

- localhost
- port number = 3333

i get error 63

what do i do wrong?

Thanks,
Tonia
0 Kudos
Message 1 of 4
(5,048 Views)
Tonia Papadogiorgaki wrote:

> Hi all,
>
> i do Application Reference & Open Application with the following inputs:
>
> - localhost
> - port number = 3333
>
> i get error 63

The error is occurring because there is no active listener at that port to
respond to the connection request. Two possible reasons:

- LabVIEW's VI Server is not currently configured to use the TCP/IP
protocol; check Edit >> Preferences, VI Server Configuration to make sure
that the TCP/IP protocol box is checked
- The TCP/IP protocol is enabled, but VI Server is listening at a different
port--3363 is actually the standard port, unless you've changed that
setting. Again, check the VI Server Configuration panel under LabVIEW
Preferences to make sure.

Regards,
John Lum
National Instruments
0 Kudos
Message 2 of 4
(5,048 Views)
John Lum wrote:
>Tonia Papadogiorgaki wrote:>>> Hi all,>>>> i do Application Reference &
Open Application with the following inputs:>>>> - localhost>> - port number
= 3333>>>> i get error 63>>The error is occurring because there is no active
listener at that port to>respond to the connection request. Two possible
reasons:>>- LabVIEW's VI Server is not currently configured to use the TCP/IP>protocol;
check Edit >> Preferences, VI Server Configuration to make sure>that the
TCP/IP protocol box is checked>- The TCP/IP protocol is enabled, but VI Server
is listening at a different>port--3363 is actually the standard port, unless
you've changed that>setting. Again, check the VI Server Configuration panel
under LabVIEW>Preferences to ma
ke sure.>>Regards,>John Lum>National Instruments>>

TCP/IP protocol box was not checked....

I have checked it and now i get error 1032 (VI server access denied)

I have the following structure: i work with RT 7030/6030E & LabVIEW RT 5.1,
and want to download a VI to the processor of RT. I want to do it from the
PC (= Host PC)
(LabVIEW RT has the possibility of working absolutely on the Board and not
on the PC, but i want to work in the opposite way -> not to work on the board
at all, but to download, run and control every Vi (on the board) from the
PC)

To do this i make an EXE of the VI that i want to download, then execute
the EXE (with Exec) and finally do Appl. Reference & Open Appl. Reference
with Vi path=the path of the VI that is also in EXE form (the reference is
opened for the VI and not for the EXE)

Propably there is something that i do not do or do wrong while Building Application....
Any ideas of what it might be?

Tonia
0 Kudos
Message 3 of 4
(5,048 Views)
> TCP/IP protocol box was not checked....
>
> I have checked it and now i get error 1032 (VI server access denied)
>
> I have the following structure: i work with RT 7030/6030E & LabVIEW RT 5.1,
> and want to download a VI to the processor of RT. I want to do it from the
> PC (= Host PC)
> (LabVIEW RT has the possibility of working absolutely on the Board and not
> on the PC, but i want to work in the opposite way -> not to work on the board
> at all, but to download, run and control every Vi (on the board) from the
> PC)
>
> To do this i make an EXE of the VI that i want to download, then execute
> the EXE (with Exec) and finally do Appl. Reference & Open Appl. Reference
> with Vi path=the path of the VI that is also in EXE form (the reference is
> opened for the VI and not for the EXE)
>
> Propably there is something that i do not do or do wrong while Building Application....
> Any ideas of what it might be?

I think you are getting the 1032 error due to more VI Server configuration issues.
Specifically, I think the executable might be set up not to allow VI Server access to
itself. When working with the built executable on the Host PC, you might see that you can
control the VI Server access settings by doing Edit >> Preferences, and working with VI
Server: Configuration, TCP/IP Access, and Exported VIs. If you check, you'll see that any
change to these settings is stored in an .INI file that is created in the same directory as
the executable.

The most "wide open" possible access settings for VI Server will results in the following
..INI file:

[APPLICATION]
server.tcp.enabled=True
server.tcp.port=3333
server.tcp.access="+*"

In order to avoid access-related errors with the executable on the target board, I think
you simply need to create an .INI file with these lines and put it in the same folder as
the executable. Make sure that the first line has your executable name between the
brackets, instead of the word "APPLICATION."

I'd suggest playing around a little more with accessing an executable via VI server when it
is residing on the Host PC, so that you can perhaps observe the process a little more
closely and get comfortable with it.

Hope it helps,
John
0 Kudos
Message 4 of 4
(5,048 Views)