LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1379 with Vi Server

Solved!
Go to solution

Hi,

 

I had some problem to setup my PC to run an application as a VI Server. I always had the error #1379 "LabVIEW:  The user failed a security authentication check." when my client vi tries to connect to the Vi Server.

 

We contact NI to have some inputs and the answer was:

 

...Another thing we can try is to put the device driver you are using on the

server computer. According to this discussion forum, this resolved the

error for some other customers of ours.

Error 1379 in Open Application Reference

http://forums.ni.com/t5/LabVIEW/Error-1379-occurred-at-Open-Application-Reference/td-p/356144/page/2...

 

So I try to install logos.mis that I found on the first CD of NI Device Drivers (D:\products\shared\logos\logos100). The problem: the logos installer starts but I obtain an empty window when they ask to select features to install (see picture attached) ???

 

22695i8C44FA0AEFD9F328

 

 

The followup by NI was to tell us to install NI-DAQmx 8.1. So, I install all default compoments suggested by the NI-DAQmx 8.1 installer.

It works!

 

But we need to install the minimum drivers on the PC that will run the app Vi Server.

 

My question is:  Why the logos installer gave my an empty features window (if it suppose to solve my problem)? And, what is the compoment installed on the server by NI-DAQmx 8.1 that solve the problem?

 

 

Application (exe) is running under a PC

OS: Windows XP Sp2 or Microsoft Server 2003 Sp2

Dev. with Labview 8.0.1

Labview Runtime copied (all needed dll are copied locally next to the app)

NI-VISA 3.6 installed

 

Regards,

0 Kudos
Message 1 of 5
(4,668 Views)

This may be repedative, but are you able to verify that your issue was not solved using this KB? Fundamentally, the problem might be stemming from the fact that most of our drivers are an amalgamation of several smaller installers that aren't intended to be run on their own, necessarily. You might use a tool such as dependency walker to track down any files the installer is calling into.

Verne D. // Software R&D // National Instruments
0 Kudos
Message 2 of 5
(4,642 Views)

Hi Verne D,

 

My ViServer:MachineAccess was previously set with "*". My problem was resolve by the only fact to install NI-DAQmx 8.1 on the PC that's run the VIServer.

 

I saw in few posting that by only installing logos.msi (without any problem I supposed) solve the problem err #1379...

 

The thing is that I am not able to use the logos.msi : no features to install available (see picture at the beginning of the thread).

I want to install the minimum on my server PC, not all the NI-DAQmx 8.1 drivers.

 

NOTE that I solve the problem by installing default compoments suggested from NI-DAQmx 8.1 (it install over 75 compoments!).

 

How to know the only compoments (or mayby 2 or 3) needed to make the Vi Server running?

 

Regards,

0 Kudos
Message 3 of 5
(4,630 Views)
Solution
Accepted by topic author lajf

I looked a bit more at this, and the list doesn't populate on any version of Logos as it's not intended as an installer that requires user configuration. If you continue through the installer, though, the component should install anyway. Give that a shot and post back with your results?

Verne D. // Software R&D // National Instruments
0 Kudos
Message 4 of 5
(4,616 Views)

Hi Verne D,

 

To verify this, I removed all NI-Drivers from the PC used as server and verify that I obtain the same err #1379 with my client VI when trying to connect.

 

After that, I install only the logos.msi and press Next butten even if there is nothing to select in the features window and it starts the installation.

 

Try to connect to my VI Server and it works!

 

Thanks,

0 Kudos
Message 5 of 5
(4,600 Views)