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
Similar Messages
-
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
LucieThe 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? -
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 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 -
高手快帮忙谢谢
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 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 -
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 KBDarin, 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? -
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 KBMost 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 compiling a library, Kernel32.dll
Attachments:
error LabVIEW82.jpg 30 KBHey elnibjo;
This error seems to be the result of the application builder not being able to find the rc file I suggest you follow the steps listed in the following KB:
Error Creating Source Distributions Involving rc Files
(http://digital.ni.com/public.nsf/allkb/833BFD5E9CA0224886257584004DAA4C)
Alternatively you can change the path information in the CLFN to contain only the DLL name.
Let me know if this works
Good luck with your applibation! -
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????????? -
App. builder Error 1003 occurred at ..... internal.llb
Hi,
I have an RT application that uses three FPGA PXI-7831R. The application was created with LabVIEW 7.0. We upgraded to 7.1, then to 7.1.1. We followed the instructions for 7.1.1, mass compile LabVIEW and mass compile our own code.
For the FPGA I had to create projects. I built the loads for each of them, updated the Open FPGA References in the RT code and then I was easily able to build an EXE with application builder. However, that load contained errors, so I had to debug it. I changes aliases in the FPGA projects, recompiled the 3 FPGA loads and refreshed their references in the RT code. I was able to debug the code and solve all my problems. That load would run with LabVIEW environment, downloaded to the RT target.
However, with application builder, when I compile that new load, I get: Error 1003 occurred at … internal.llb… The VI is not executable. I verified the VIs and their arrows are not broken. I already had "BldApp.RemovePolyVIsandTypedefs=False" in LabVIEW.ini. I opened my RT top level VI and performed ctrl-shift-run and LabVIEW becomes not-responding, taking 99% of the CPU, in that state for 90 minutes. I repeated that with a lower level VI containing FPGA Read/Write Control and got the same behavior, ctrl-shift-run makes LabVIEW to process I don't know what until I kill it. I could repeat that on 2 more PCs. However, it is ok if I do that with a VI not containing FPGA references.
The VI stated to be non-executable contains call to FPGA Read/Write Control. I removed these calls to debug and I got the same Error 1003 on the next VI containing an FPGA Read/Write Control. Are there some known issue with application builder and accessing FPGA with LabVIEW RT 7.1.1?
Thanks!Hi, AvernaFrca
You shouldn't have any problems when creating an EXE in LabVIEW that calls the Open FPGA VI Reference or the Read/Write Control VI. There are a few KBs online that relate to that error number, but it seems that you have read them already, because the suggested fixes are to mass compile (or do Ctrl + Shift + R) and that doesn't seem to fix it for you.
In your case, I would recommend you to make sure that your VIs are not corrupted. The easiest way will be to create another FPGA VI that you could call from a brand-new host VI. It can be something as simple as just do A + B. If that does work, then it might be a problem with your current VIs and it might be a good idea to recompile them, just to make sure. Hopefully that will take care of it. If the error is still present, then the problem might be the actual Read/Write Control VI, and we will have to fix or replace it with a new one.
I hope this helps! Let me know if you have any additional information.
GValdes -
Error 1003 occurred at Invoke Node
Good morning.
I work with LW8.5 and created with the following architecture:
There is main.vi on the links at the user's calls and runs the other VI.
That is, not directly, these are not included in the VI block diagram main.vi.
In the development of a happening in normal mode, all dynamically called VI,
But once I make EXE, when you try to call the dynamic VI error 1003.
Error 1003 occurred at Invoke Node in Main.vi
Possible reason (s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>> Open and verify that it is runnable.
VI Path: C: \ Shaikov \ Labwiev \ builds \ NSIAES \ Initialsettings \ Initialsettings.vi
Show you how to act?
Thank you.Hello margasan.
In my Projects I use to pass more dynamic and VI classes.
In the attached file - an example of my project:
In the main folder is a folder UpperClass, it is the parent class and child classes and HeirClass.lvclass Heir2Class.lvclass are organized into folders respectively Plugin1 and Plugin2, and these Classes inherit from the parent one and the same WI - UpperClassTest.vi. Plus, this Plugin1 has two, independent from the others, but related classes. A block diagram for an object placed Core.vi UpperClass.
So, here, if you take EXE, making llb files and run them from start VI for each of the Plugin, then everything works OK.
But as soon as I on the block diagram of a Plugin will put any object UpperClass, or one of its nasalednikov, there arises a familiar ERROR 1003. Prompt, plc, margasan I get rid of it in this case?
Attachments:
Example.zip 1481 KB -
Error 7 occurred at Open/Create/Replace File in Open Config Data.vi
I have a .vi that was working fine with Labview 7.0. I now have upgraded to Labview Professional 8.0, and I am trying to build a stand alone executable. When I build the executable, build an installer, and then try to install it on another computer then run it......... I get the "Error 7 occurred at Open/Create/Replace File in Open Config Data.vi" error. Any ideas?
Hello,
In addition to the LabVIEW Help, there is an Application Note on Distributing Applications with the LabVIEW Application Builder and a knowledge base article What Is The Build Specification Feature In Application Builder? that might be helpful.
Also, here
is a knowledge base article on what Dennis has described and it
provides an example to call an extra Strip Path function. Also, instead
of using a Match Pattern function, you could use the App.Kind property
node (use Open Application Reference, Property Node: Application ->
Kind, and Close Reference) to determine if you are running in a
Run-time system.
Good luck and best regards,
Shakhina P.
Applications Engineer
National Instruments -
Error 7 occurred at open/create/replace file
Hello,
I have searched the forum and could not find any useful information regarding my problem, so hope you may shed some light. MyVI can create a new csv (text) file by using the time to name the file, so every time the new file will be created with a different name and file path is not a relative path. I can run the VI in both development environment and stand along executable without any problem. But,
One of my colleagues cannot run the executable exe on her machine because Error 7 occurred at Open/Create/Replace File in xxxx.vi Possible reason: LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
My question is why only she cannot run this exe on her machine. I have checked a few different PC in my office and all of them can run this exe without problem, so I am pretty sure the code is fine.
I have already ask her to do,
Run the executable as administrator
Save the new file to other drives (not C: drive)
but she still cannot run the executable. I dont think this is a premission issue, otherwise, LabVIEW would give a different error, Error 8 I believe.
Both her PC and my PC is running Windows 7 professional 64-bit. The only difference I can see is that she is based in US and I am based Australia. Does anyone have any idea? Please help.
Thanks,
ShermanI’m not sure but expecting like below,
As you said, your creating file name with Time. Make sure file name is correct and there is no special characters (like, / or : ). If your formatting time to string with “Format Date/Time String.vi” (while creating file name), based on UTC format, string will change.
UTC format specifies if the output string is in Universal Time or in the configured time zone for the computer. If TRUE, date/time string is in Universal Time. The default is FALSE.
Make sure you have access rights to create files into mentioned folder. Try to create new file manually.
Munna
Maybe you are looking for
-
Lightroom 1.4.1 Has anybody experienced corrupt print driver using Mac OS X Tiger
Hi folks, I am starting to pull hair out! Whilst nearing the end of a print run for a wedding customer, my HP B9180 has begun to print what looks like dark lines on 'some' areas of my prints. I have done all that I can to resolve this but to no avail
-
Hi, Im useing Hp Pavilion Dv9000 , recentlly i bought Philips PC Headset SHM1900 for using skype ...when i pluged both the mic and speaker pins in the slot,i can hear music and others but mic not working...i tried all the options in control pannel fo
-
i
-
Type on a path, object flipped?
I flipped an object horizontally. Now, I need to apply type on a path to the object, but when I do so the type also appears flipped, even though the type was applied AFTER I flipped the object. How can I get the type to read correctly?
-
IOS devices, the 3 screen resolutions
iphone4, 4s, ipod 4th gen ipad 1 and 2 3Gs , ipod 3rg gen (3rd gen 16+ gig only right?) 1) Within these three matching resolution catagory's, can i assume an app will always layout identical? To elaborate, if i have an app with retina display running