LV 8.2.1 Error 66 or 1379 occured at open Application Reference. A LV 8.2.1

[Salvator]

Hi,

LV 8.2.1 Error 66 or 1379 occured at open Application Reference. A LV 8.2.1

Using:

Application access an other LV application on an remote PC with Vi-Server Technology. (Based on MS OS Windows XP SP2 with all patches ...)

With LabVIEW 8.2.1 it is not possible (exactly: with one PC it works, with other PCs, (identical regarding configuration of LabVIEW-Components), the described errors occured ...

There is no problem with LV 7.1.1. ( If the VI-Server Configuration of the .exe will be done within the .ini -File...)

The differences between LV 7.1.1 are in the .ini-File of the application regarding the the access-List property.

Error 66 occures if ther is no entry in the access-List property.-> OK.

Error 1379 occures if i will use the copy of the LV .ini-File acl-property with allowed access from all clients (*) or special clients defined with IP-Adress ... -> BUG

The same behaviour is described in 2 threads in the discussion forum ..., but in my application/configuration the workaround acl.configuration: "allow access from all clients" will work only with one PC ?

So what is the solution ?

At this moment i gol back to LV 7.1.1, but this is surely not the solution ....

Thanks for help ....

[Plamen]

Hi!

I have also found following discusion in the forum.

But the the problem for Error 1379 lies in LabVIEW 8.2.1 and VI Server.
This is a know Bug. This Bug should be fixed in a future version.
The problem is that the IP address in the could not be resolved into a machine name.

Workaround:
This program works in 7.1 so the only option right now is to use 7.1 instead of 8.2.1.

Plamen

Message Edited by Support on 10-31-2007 08:59 AM

[Salvator]

Hi,

is it really a known bug ?

Exists an error ID for the Bug ? What does NI said to the problem ?

In which future version ( > 8.5.x) and when is the fix to be expected ?

I think the VI-Server Technology is a main feature of LabVIEW and it is not acceptably to uses the old LV 7.1.1 version.

Question: If the error causes regarding the resolve of the machine name ( I uses IP-adresses ... ) is there a possible workaround

to configure the IP environment ?

Thanks a lot for help.

Salvator

[Plamen]

Hi Salvator,

I'm from NI. 🙂

This is a known Bug and the only Workaround for this problem is to use LV 7.1.

On your question about BUG ID and in which LabVIEW Version
the bug will be fixed I am not allowed to give you detailed Information.


Plamen

[Salvator]

Hi Plamen,

thank you for the answer, now i understand the problem and i will continue with the LV 7.1.1 workaround in my application.

Salvator

[Ben]

Hi Plamen,

I understand you can not reveal when the bug will be fixed.

You are allowed to share the CAR#.

Please post the CAR# for this bug.

Thank you,

Ben

[Plamen]

the CAR ID is:
49G8P500

Plamen

[Ben]

Five stars to you!

I like CAR#'s

Ben

[Salvator]

Hi Ben , Plamen

is there something, which i have to know regarding the CAR ID ?

What does it mean "CAR" ?

Ben, why do you "like" CAR#s ?

In the Bug Fix List (8.5 to 8.2.1) and the Known Issues (LabView 8.5) i can`t find this ID.

Please try to make me a little more smartly ...

Salvator

[Ben]

CAR = Corrective Action Report

I use them to track repots of bugs (like this thread) and which version of LV they get fixed in.

Since you did not find this in any of the lists you looked at this means that this bug is new and at least the "Known Issues" should be updated.

Ben