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

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 ....

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
National Instruments Germany
Application Engineer

Similar Messages

Error 1379 occurred at Open Application Reference

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

Swap your network cables. LabVIEW VI Server binds itself to the first network card it sees and will not talk to your second card. So, make sure the the remote machine you are talking to can be reached via the first network card listed by Windows.
This is definily a bug in VI Server but I don' think NI has any plans to fix it.
-John
-John
Certified LabVIEW Architect

Error 7 occurred at open vi reference in New Report.VI

Hello!
I use the report generation toolkit on LabView 7.0 to create a report in Excel. The program works fine until I make an executable version. I the get the error:
Error 7 occurred at open vi reference in New Report.VI
I use the New Report.VI, Bring Excel to front.VI and Save Report To File.vi
Can you pleace help me!!!

Most likely, you did not include the required libraries in your build script. When building an executable in which you use the Report Generation Toolkit, you must include the _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs on the Source Files tab.
Check this article for more info.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
Daniel L. Press
PrimeTest Corp.
www.primetest.com

Error 7 occurred at Open VI Reference with Application Builder

Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
"Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

Dear Sir;
There are two things that are good to try:
First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
.llb file to compile.
Regards

Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi- Dist Build LLB Image.vi- Dist Build App Image.vi- Build Application.vi

When trying to build an application using labview 7.1 and windows XP, I get the error
Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
I've tried the crtl-shift-run as well as a mass compile and I still get the error.
Any ideas?
Thanks,
Mike

Hopefully this thread, or this KB article might help.
It seems like this could come from a lot of things, but there's suggestions in those which might lead you in the right direction
Message Edited by Day on 09-22-2006 02:07 PM

高手快帮忙谢谢labview7打包后用到7中新的new report.vi的地方(选择的是word)都提示error 7 occurred at open vi reference in new report.vi

高手快帮忙谢谢
labview7打包后用到7中新的new report.vi的地方（选择的是word）都提示error 7 occurred at open vi reference in new report.vi。
下面提示的可能原因是Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on UNIX.
我愿自己是个胡萝卜，可以自己自足啦!

我明白您的意思，也可以按您所说的作，
但是open vi peference这个vi是labview提供的标准new report.vi的子vi中使用到的，如果我手动修改open vi peference中的提供的word路径，也就是说labview提供的模块也要自己修改了??
我愿自己是个胡萝卜，可以自己自足啦!

Error in open Application reference

Hi all,
I got an error when trying to open application reference in a VI with TCP/IP port number configured as in below image.
I tried it running multiple times. I got the same error. When I logged off and logged in again, it works fine.
Can anyone tell me the reason for this?
LabVIEW version:2010
I
Thanks,
Suresh

Did you change any of the VI server settings?
I'm pretty sure LabVIEW has to restart in order for any of those changes to take effect.

Error 1003 occured at Open VI Reference

This error occured when I want to used the LabView Report Generation Toolkit for Microsoft Office Example.
It's impossible for me to execute the example "Generate Report from Template(Excel)"
I suppose I have a problem with the Open VI Reference.vi function but I don't know where is that VI.
Could you let me know where are the VIs listed in the Application Control Pallette.
Do you know why I have this type of problem.
Thanks
Lucie

The VIs located on the application control palette are primitives and are part of LabVIEW itself. Therefore you can not look at their diagrams because they don't have one.
However the 1003 error means that you are trying to dynamically load a VI that is not executable. I would suggest turning highlight execution on and following the code to see what path is sent into the Open VI reference function.
Once you have the VI that is failing to open go manually open it.
Chances are that it is broken, so see why it is broken. If I remember correctly there is a linking issue in that example, so you can open the VI that is broken and hit ctrl-shift-Run Button, and that should relink it all and fix the issue.
If not take a look at this
Why Do I Get Error 1003 From Application Builder When I Try to Build Excel Macro Example.VI?

Error -1074388957 occurred at Open DeviceNet Interface.vi

I keep getting the following error message
Error -1074388957 occurred at Open DeviceNet Interface.vi
Possible reason(s):
NI-CAN: (Hex 0xBFF62023) The Interface is invalid or unknown. Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
=========================
NI-Industrial Communications for DeviceNet: (Hex 0xBFF62023) The Interface is invalid or unknown. Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
Here is my system Info:
Windows 7 Pro 64
LabVIEW 2010 32 bit
PCI-CAN card
Drivers Installed: NI Device Net 1.6.7, NI-IndCom for Devicenet 2.2, NI-CAN 2.7.5
Thanks for any help!

I noticed that there are two sets of devicenet VI libraries in my LabVIEW 2010 vi.lib directory that have the same name. The supposedly correct one that LabVIEW automatically places on the block diagram from the palette is from the "DeviceNet" folder. This one gives the error described earlier when I run it. There is another one in the "Nidnet" folder with the same name and this one works and does not give an error. TheNidnet one appears older since it has the older looking front panel objects.
Does not work (error hex BFF62023):
C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\DeviceNet\VIAPI\Open DeviceNet Interface.vi
Works:
C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\Nidnet\Nidnet.llb\Open DeviceNet Interface.vi
It is correct to use the nidnet folder with LabVIEW 2010 and newer or should I be using the DeviceNet folder version. If the nidnet version is the correct one, is there a way to make it so these appear on the palette when I go to add them to the block diagram?
Any thoughts?

Error 7 occured at Open VI Reference in

The error is actually displayed after each and every Printer VI like SetMagins, PageSize, AddField, CloseReport but NOT after the NewReport.vi Call!

This error means that it can't find the file that you are trying to open a reference to. The file could either be missing or the path to it could be wrong.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Error PLS-00355 occurs when open cursor in procedure

Hello everybody,
I have a problen that really drives me mad:
Whenever I try to compile the following procedure, the Error "PLS-00355: use of pl/sql table not allowed in this context" occurs but I can't see what is wrong. I hope the wisdome of the community will help to solve the problem.
Here is the code:
CREATE or REPLACE PROCEDURE data_year(study_year IN NUMBER) AS
sep CONSTANT CHAR := ';';
CURSOR cursor_year(year_of_interest NUMBER) IS
select
BBS_CONDITIONS.COUNTRYNUM as country,
BBS_CONDITIONS.STATENUM as state,
BBS_CONDITIONS.ROUTE as route,
BBS_ROUTES.LATITUDE as lat,
BBS_ROUTES.LONGITUDE as lon,
BBS_SUMMARY.AOU as aou,
BBS_SPECIES.ENGLISH_COMMON_NAME as name,
BBS_SPECIES.MIGRATION_TYPE as migtype,
BBS_SUMMARY.SPECIESTOTAL as count,
BBS_CONDITIONS.MONTH as smonth,
BBS_CONDITIONS.STARTTIME as starttime,
BBS_CONDITIONS.ENDTIME as endtime,
BBS_CONDITIONS.RPID as rpid,
BBS_CONDITIONS.ASSISTANT as assistant
from BBS_SPECIES,
BBS_ROUTES,
BBS_SUMMARY,
BBS_CONDITIONS
where BBS_ROUTES.ROUTE = BBS_CONDITIONS.ROUTE
and BBS_ROUTES.STATENUM = BBS_CONDITIONS.STATENUM
and BBS_ROUTES.COUNTRYNUM = BBS_CONDITIONS.COUNTRYNUM
and BBS_SPECIES.AOU = BBS_SUMMARY.AOU
and BBS_CONDITIONS.YEAR = BBS_SUMMARY.YEAR
and BBS_CONDITIONS.ROUTE = BBS_SUMMARY.ROUTE
and BBS_CONDITIONS.STATENUM = BBS_SUMMARY.STATENUM
and BBS_CONDITIONS.COUNTRYNUM = BBS_SUMMARY.COUNTRYNUM
and BBS_SPECIES.CLASS_ID = 0
and BBS_CONDITIONS.YEAR = year_of_interest
order by country, state, route, migtype, aou;
rec_year cursor_year%ROWTYPE;
i NUMBER := 1;
TYPE table_year_type IS TABLE OF cursor_year%ROWTYPE;
table_year table_year_type;
BEGIN -- Begin of procedure data_year
table_year := table_year();
OPEN cursor_year(study_year);
LOOP
FETCH cursor_year into rec_year;
EXIT WHEN cursor_year%NOTFOUND;
table_year.EXTEND(1);
table_year(i) := rec_year;
i := i+1;
END LOOP;
CLOSE cursor_year;
DBMS_OUTPUT.PUT_LINE('country' || sep || 'state' || sep || 'route' || sep || 'lat' || sep || 'lon'
|| sep || 'aou' || sep || 'name' || sep || 'migtype' || sep || 'count' || sep || 'month' || sep
|| 'starttime' || sep || 'endtime' || sep || 'rpid' || sep || 'assistant');
FOR i in table_year.FIRST..table_year.LAST LOOP
DBMS_OUTPUT.PUT_LINE(TO_CHAR(table_year(i).country) || sep || TO_CHAR(table_year(i).state) ||
sep || TO_CHAR(table_year(i).route) || sep || TO_CHAR(table_year(i).lat) || sep ||
TO_CHAR(table_year(i).lon) || sep || TO_CHAR(table_year(i).aou) || sep ||
table_year(i).name || sep || TO_CHAR(table_year(i).migtype) || sep ||
TO_CHAR(table_year(i).count) || sep || TO_CHAR(table_year(i).smonth) || sep ||
TO_CHAR(table_year(i).starttime) || sep || TO_CHAR(table_year(i).endtime) || sep ||
TO_CHAR(table_year(i).rpid) || sep || TO_CHAR(table_year(i).assistant));
END LOOP;
END; -- End of procedure data_year
Thanks ahead, TC

Does it give a line number? I'm wondering if it might be
table_year := table_year();
that's causing the problem. Try removing it and see.
Even better, change your code to
   TYPE table_year_type IS TABLE OF cursor_year%ROWTYPE INDEX BY BINARY_INTEGER;
   table_year     table_year_type;
BEGIN
    OPEN cursor_year (study_year);
    FETCH cursor_year BULK COLLECT INTO table_year;
    CLOSE cursor_year;
...Edited by: Dave Hemming on Nov 21, 2008 9:51 AM

Error 1004 occurred at Open VI Reference in Directory of Top Level VI.vi- Check Path.vi- Read PNG File.vi- ValveUI.xctl:LoadBackgroundImage.vi- ValveUI.xctl:Facade 1.vi:29- ValveUI.xctl:Facade 1.vi.ProxyCaller

I am trying to dynamically load the background image of an XControl facade using a 'LoadBackgroundImage.vi' that I have written. This SubVI has worked with a normal VIs panel before. It utilizes the 'Read PNG File.vi' from Labview to read in a transparent PNG file to overwrite the Facade background. When the XControl is loaded during design-time it generates an Error 1004 indicating that the 'Read PNG File.vi' is not in memory. I have tried to place a static reference to this vi to force it to load but I still get this error. What is the solution?
Attachments:
Error Dialog.PNG ‏9 KB
LoadBackgroundImage_VI.PNG ‏33 KB

Darin, thanks for your reply.
The XControl Facade is rendered on the Main FP when the Main.vi is opened in design mode. Previously I have placed a PNG image onto the Facade pane (i.e. drag-n-drop the image onto the Facade FP during design) and it is displayed on the Main.vi FP in design mode when Main is loaded. However, when I include a call to Read PNG File.vi in the Facade I get the 1004 error. You may not see this error without using a Simple Error Dialog. This failure to find Read PNG File.vi in memory is the main issue.
I have tried to use SubPanels before - they are useless for my purposes for many reasons (they don't show the underlying SubVI pane in design mode, they require the use of SubVI references to load - preventing the use of direct wiring to the SubVI connector, etc.).
Do you know how to dynamically load and call 'Read PNG File.vi' so that Labview is forced to load the VI and then Read PNG File can load the PNG image? I can get 'Read PNG File.vi' to dynamically load and show property values but to call it with the 'Call By Reference Node Function' I need a strict type def to be generated, etc. So what are the steps needed to create a dynamic call to 'Read PNG File.vi'? I haven't seen any good working examples that show how to create the strict typedefs that are required etc. There is no right-click > Make Type Def > ... for Read PNG File.vi or other ways to do this that I have noticed. Showing a finished example doesn't show you how to do it (menu selections, etc.). Or, do I have to hand construct these typedefs by reverse engineering the VI?

Error 1031 occurred at Open VI Reference in. This error occured in the ni5640R Template Config ADC (FPGA).vi

When I tried to open the ni5640R Template (FPGA).vi I got this error
Message Edited by 09441213131 on 05-23-2009 02:42 AM
Attachments:
error.JPG ‏135 KB

Most likely, you did not include the required libraries in your build script. When building an executable in which you use the Report Generation Toolkit, you must include the _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs on the Source Files tab.
Check this article for more info.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
Daniel L. Press
PrimeTest Corp.
www.primetest.com

I'm getting an "Error 1003 occurred at Open VI Reference in Dist Call Create Installer.vi- Build Application.vi." whenever I try to create an installer for my app.

I'm running LabVIEW 6.1 on Win XP Pro, and my application
builds fine, but I can't create an installer.

Dependency Walker will show all of the DLLs NIMSIDistKit.dll is dependent on. There is a tree view in the top but the flat list at the bottom will probably be more helpful. It should show the following dlls (at least on a Windows 2000 system):
ADVAPI32.DLL
GDI32.DLL
KERNEL32.DLL
MSI.DLL
NIMSIDISTKIT.DLL
NTDLL.DLL
OLE32.DLL
RPCRT4.DLL
USER32.DLL
If one of these DLLs is missing it will have an error message displayed beside it. I think all of them are regular Windows DLLs so if you are missing one of them your computer might be having other problems. You could try to reinstall LabVIEW to see if it will install a copy of the dll, but you might have to reinstall Internet Explorer or some portion of the OS to get all
of them.
Probably the most important dll is the MSI.dll. If it is missing or too old it might be the problem. I have version 2.0 but I think version 1.1 of this DLL will also work. If you don't have the dll or the right version run \applibs\distkit\redist\InstMsiW.exe (if on Win NT/2000/XP) or InstMsi.exe (95/98/ME). This will install/update MSI (Microsoft Installer) on your machine.
You can also press F9 to toggle showing just the filename and the whole path to the dlls. Besides NIMSIDistKit.dll all of them should be loading from your system folder. If not you may have multiple copies of that DLL and the correct one is not being found.

Error 42 occurred at Open Application Reference in DynamicDownload.vi

Hi！
I want to create an executable from a VI wich calls a dll created by Simulink and Simulation Interface Toolkit.
After I compile the simulink module with MSVC++ 6.0 in MATLAB,and then use this dll in LabVIEW,
the following message appears:
Error 42 occurred at Open Application Reference in DynamicDownload.vi->SIT_InitEstablishTCPConnection.vi->SIT Initialize.vi->Untitled.vi
Returning to Select Host dialog.
Possible reason(s):
LabVIEW: Generic error.
What should I do to have an executable which works correctly?

I have the same Problem here with the Error 42 on open application reference.
Can someone pleas explain what this error means, and what the reasons are for this error?
I have two exe files, and i am trying to open the application reference of the other exe when i get this error.
First i thought it has something to do with the .ini file settings, which by the way is nowhere explained...
here my entries:
server.tcp.acl="290000000A000000010000001D00000003000000010000002A10000000030000000000010000000000"
server.tcp.enabled=TRUE
server.tcp.port=3360
server.tcp.serviceName=Image Monitoring
server.tcp.access=+*,"+*","127.0.0.1","Localhost"
server.vi.access=+*
server.vi.callsEnabled=TRUE
server.vi.propertiesEnabled=TRUE
server.ole.enabled=TRUE
server.tcp.paranoid=TRUE
server.tcp.servic=My Computer/VI Server
tcpServer.log=TRUE
tcpServer.logPath=c:\TestStand\Tools\Image Monitoring PC\serverlog.txt
server.app.propertiesEnabled=TRUE
if i build a simple exe with call on open applicationr eference it works. but not with my main application,
so this is why i need to know what causes the Generic Error???
Is there a possibility that there have to be certain entries in the ini file of the calling exe? and what would those entries be?????????

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

Similar Messages

Maybe you are looking for