I have a VI server running in a executable made in LV8.0. When I try to
Open Application Reference in a client in LV8.0, I get the error 1379:
LabVIEW: The user failed a security authentication check.
I worked a long time with the same server in an executable of LV6, and
I can call it from the same LV8.0 I was using to test my new server. It
works fine.
Somebody knows if I have to allow access to the RT application, or
something like that?
I'm using Windows 2000 NT Professional, SP4.
Thanks,
Henrique
Henrique,
Make sure that you have allowed access to your VI server. You can do this by going to tools>>Options>>VI Server Machine access, and VI Server: Exported VIs. Try adding a "*" (no quotes) to the list and see if that helps. Also make sure you don't have a firewall that could be blocking communications. Lastly, Make sure you are using the most recent version of RT and LabVIEW. Post to let us know!
Chris C
Hi Chris C
Thank you for the reply. I'm using the 8.0 RT of LV.
I set the allowed clients and VIs for the communications when I start
the server, wiring the name of the clients and VIs with a '+' in the
beginning of them to the Server.TCPAccess and Server.VIAccess terminals
of the server's Property Node of the application reference.
Following your suggestion, I appended the '+*' to the TCP clients list,
but the same error continue. The server log has the lines below:
2006.08.15 - 12:06:50; ## New incoming connection
CONNECTION ACCEPTED; client="150.162.165.74" (150.162.165.74)
2006.08.15 - 12:06:50; ## Receiving message
hdr={err= 0; uID=0x00000006; len= 36; msg="kTSClientSaysHeaveno"(0)}
conn @0x24A37D8; cookie=0x5FB00000; "150.162.165.74"
2006.08.15 - 12:06:50; ## Closing connection
SERVER closing ref=0x5FB00000; "150.162.165.74"
The computer I ran the client side is with problems in the system time.
I'll try in other equipment too, and with other users to see what
happens, and then I post the result here.
Thanks!
Chris_C. escreveu:
> Henrique,
> Make sure that you have allowed access to your VI server. You can do this by going to tools>>Options>>VI Server Machine access, and VI Server: Exported VIs. Try adding a "*" (no quotes) to the list and see if that helps. Also make sure you don't have a firewall that could be blocking communications. Lastly, Make sure you are using the most recent version of RT and LabVIEW. Post to let us know!
>
> Chris C
I'm having this problem for a (very) long time... now it's solved.
In the LV8, a user and domain security manager was added:
http://zone.ni.com/reference/en-XX/help/371361A-01/lvupgrade/labview_8_0_features/#Logging_In_and_Out_of_LabVIEW
To solve the problem, you need to add a domain and users with the
permissions you want at the server, and log in. In the client, no
change is required.
My problem now is to manage the domain only with the RT, because my
server is an executable. Does anybody know if it's possible?
Thanks!
Henrique Menarin escreveu:
> Hi Chris C
>
>
> Thank you for the reply. I'm using the 8.0 RT of LV.
>
> I set the allowed clients and VIs for the communications when I start
> the server, wiring the name of the clients and VIs with a '+' in the
> beginning of them to the Server.TCPAccess and Server.VIAccess terminals
> of the server's Property Node of the application reference.
>
> Following your suggestion, I appended the '+*' to the TCP clients list,
> but the same error continue. The server log has the lines below:
>
> 2006.08.15 - 12:06:50; ## New incoming connection
> CONNECTION ACCEPTED; client="150.162.165.74" (150.162.165.74)
> 2006.08.15 - 12:06:50; ## Receiving message
> hdr={err= 0; uID=0x00000006; len= 36; msg="kTSClientSaysHeaveno"(0)}
> conn @0x24A37D8; cookie=0x5FB00000; "150.162.165.74"
> 2006.08.15 - 12:06:50; ## Closing connection
> SERVER closing ref=0x5FB00000; "150.162.165.74"
>
> The computer I ran the client side is with problems in the system time.
> I'll try in other equipment too, and with other users to see what
> happens, and then I post the result here.
>
> Thanks!
>
>
>
> Chris_C. escreveu:
>
> > Henrique,
> > Make sure that you have allowed access to your VI server. You can do this by going to tools>>Options>>VI Server Machine access, and VI Server: Exported VIs. Try adding a "*" (no quotes) to the list and see if that helps. Also make sure you don't have a firewall that could be blocking communications. Lastly, Make sure you are using the most recent version of RT and LabVIEW. Post to let us know!
> >
> > Chris C
It's possible. The Manager is called by either LV or RT from Windows:
http://groups.google.com.br/group/comp.lang.labview/browse_thread/thread/3bbdb122ae957d72/481a03609a0f676
An example of how to do:
http://digital.ni.com/public.nsf/websearch/4B1E01877B4A398786256B030057A4B0?OpenDocument
Henrique Menarin escreveu:
> I'm having this problem for a (very) long time... now it's solved.
>
> In the LV8, a user and domain security manager was added:
> http://zone.ni.com/reference/en-XX/help/371361A-01/lvupgrade/labview_8_0_features/#Logging_In_and_Out_of_LabVIEW
>
> To solve the problem, you need to add a domain and users with the
> permissions you want at the server, and log in. In the client, no
> change is required.
>
> My problem now is to manage the domain only with the RT, because my
> server is an executable. Does anybody know if it's possible?
>
> Thanks!
>
>
>
> Henrique Menarin escreveu:
>
> > Hi Chris C
> >
> >
> > Thank you for the reply. I'm using the 8.0 RT of LV.
> >
> > I set the allowed clients and VIs for the communications when I start
> > the server, wiring the name of the clients and VIs with a '+' in the
> > beginning of them to the Server.TCPAccess and Server.VIAccess terminals
> > of the server's Property Node of the application reference.
> >
> > Following your suggestion, I appended the '+*' to the TCP clients list,
> > but the same error continue. The server log has the lines below:
> >
> > 2006.08.15 - 12:06:50; ## New incoming connection
> > CONNECTION ACCEPTED; client="150.162.165.74" (150.162.165.74)
> > 2006.08.15 - 12:06:50; ## Receiving message
> > hdr={err= 0; uID=0x00000006; len= 36; msg="kTSClientSaysHeaveno"(0)}
> > conn @0x24A37D8; cookie=0x5FB00000; "150.162.165.74"
> > 2006.08.15 - 12:06:50; ## Closing connection
> > SERVER closing ref=0x5FB00000; "150.162.165.74"
> >
> > The computer I ran the client side is with problems in the system time.
> > I'll try in other equipment too, and with other users to see what
> > happens, and then I post the result here.
> >
> > Thanks!
> >
> >
> >
> > Chris_C. escreveu:
> >
> > > Henrique,
> > > Make sure that you have allowed access to your VI server. You can do this by going to tools>>Options>>VI Server Machine access, and VI Server: Exported VIs. Try adding a "*" (no quotes) to the list and see if that helps. Also make sure you don't have a firewall that could be blocking communications. Lastly, Make sure you are using the most recent version of RT and LabVIEW. Post to let us know!
> > >
> > > Chris C
Actually, I had to call C:\Program Files\National
Instruments\Security\dmanager.exe
Henrique Menarin escreveu:
> It's possible. The Manager is called by either LV or RT from Windows:
>
> http://groups.google.com.br/group/comp.lang.labview/browse_thread/thread/3bbdb122ae957d72/481a03609a0f676
>
>
> An example of how to do:
>
> http://digital.ni.com/public.nsf/websearch/4B1E01877B4A398786256B030057A4B0?OpenDocument
>
>
>
>
> Henrique Menarin escreveu:
>
> > I'm having this problem for a (very) long time... now it's solved.
> >
> > In the LV8, a user and domain security manager was added:
> > http://zone.ni.com/reference/en-XX/help/371361A-01/lvupgrade/labview_8_0_features/#Logging_In_and_Out_of_LabVIEW
> >
> > To solve the problem, you need to add a domain and users with the
> > permissions you want at the server, and log in. In the client, no
> > change is required.
> >
> > My problem now is to manage the domain only with the RT, because my
> > server is an executable. Does anybody know if it's possible?
> >
> > Thanks!
> >
> >
> >
> > Henrique Menarin escreveu:
> >
> > > Hi Chris C
> > >
> > >
> > > Thank you for the reply. I'm using the 8.0 RT of LV.
> > >
> > > I set the allowed clients and VIs for the communications when I start
> > > the server, wiring the name of the clients and VIs with a '+' in the
> > > beginning of them to the Server.TCPAccess and Server.VIAccess terminals
> > > of the server's Property Node of the application reference.
> > >
> > > Following your suggestion, I appended the '+*' to the TCP clients list,
> > > but the same error continue. The server log has the lines below:
> > >
> > > 2006.08.15 - 12:06:50; ## New incoming connection
> > > CONNECTION ACCEPTED; client="150.162.165.74" (150.162.165.74)
> > > 2006.08.15 - 12:06:50; ## Receiving message
> > > hdr={err= 0; uID=0x00000006; len= 36; msg="kTSClientSaysHeaveno"(0)}
> > > conn @0x24A37D8; cookie=0x5FB00000; "150.162.165.74"
> > > 2006.08.15 - 12:06:50; ## Closing connection
> > > SERVER closing ref=0x5FB00000; "150.162.165.74"
> > >
> > > The computer I ran the client side is with problems in the system time.
> > > I'll try in other equipment too, and with other users to see what
> > > happens, and then I post the result here.
> > >
> > > Thanks!
> > >
> > >
> > >
> > > Chris_C. escreveu:
> > >
> > > > Henrique,
> > > > Make sure that you have allowed access to your VI server. You can do this by going to tools>>Options>>VI Server Machine access, and VI Server: Exported VIs. Try adding a "*" (no quotes) to the list and see if that helps. Also make sure you don't have a firewall that could be blocking communications. Lastly, Make sure you are using the most recent version of RT and LabVIEW. Post to let us know!
> > > >
> > > > Chris C
Mega Search
Sign Up 
