Error 1003: Running a VI inside LLB from EXE

HELP!
I have a Labview Executable which is using some "plugin drivers" provided as LLB. The drivers are loaded dynamically with "Invoke Method: Run VI". My Exe does not contain any dependency to those driver LLB's. The LLB build projects are build with vi.lib. "Disconnect type def" and "Remove unused polymorphic ...." are both unchecked. Everything worked for a while without any problems. I had one driver which is using GMath:Interpolate 1D. Now I have a second driver which is using "Interpolate 2D". Those 2 driver VI's won't load at same time. It is really strange but if I disable one, the other will load. If both are active I get error 1003 indicating that some VI is not able to run mostly because of missing dependencies. I faced that message a lot in the past but this time I don't know what else to do. I tried several combinations of building the LLB's and the exe, even included those dynamic VI's into exe but all time same. I have less hope that someone here can help me but I give it a try.
BTW, is there any chance to debug and see the exact reason why my VI won't load. When I breakpoint at "Invoke Method: Run VI" i will see that it returns 1003 but can I find out more?

I have seen this happen as well in my application's plug-in architecture. It happened with a pair of different DAQmx Read VIs in our case. I filed CAR 285388 against it. It is currently under investigation. I will put the information about your issue in the existing bug report.
Right now I don't know of any workaround.
Jarrod S.
National Instruments

Similar Messages

  • Error while running ADF-BC Test Suite from command line

    Hi,
    I have created a separate test project containing the Test Suite for the Model componenet of my ADF-BC  application.
    I need to run this test project separately from jmeter.
    The tests run fine from Jdev, But when I package the test project into a jar and try to run from command line, I get the following error:
    java.lang.NoClassDefFoundError: oracle/jbo/ApplicationModule
            at com.oracle.cs.cap.module.applicationModule.ServiceAMFixture.<init>(ServiceAMFixture.java:36)
            at com.oracle.cs.cap.module.applicationModule.ServiceAMFixture.<clinit>(ServiceAMFixture.java:15)
            at com.oracle.cs.cap.module.view.EntitlementReportDurationViewVO.EntitlementReportDurationViewVOTest.<init>(EntitlementReportDurationViewVOTest.java:11)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
            at java.lang.reflect.Constructor.newInstance(Unknown Source)
            at org.junit.internal.runners.JUnit4ClassRunner.createTest(JUnit4ClassRunner.java:72)
            at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:79)
            at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
            at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
            at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
            at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
            at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
            at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33)
            at org.junit.runners.Suite.access$000(Suite.java:26)
            at org.junit.runners.Suite$1.run(Suite.java:93)
            at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
            at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
            at org.junit.runners.Suite.run(Suite.java:91)
            at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33)
            at org.junit.internal.runners.CompositeRunner.run(CompositeRunner.java:28)
            at org.junit.runner.JUnitCore.run(JUnitCore.java:130)
            at org.junit.runner.JUnitCore.run(JUnitCore.java:109)
            at org.junit.runner.JUnitCore.run(JUnitCore.java:100)
            at org.junit.runner.JUnitCore.runMain(JUnitCore.java:81)
            at org.junit.runner.JUnitCore.main(JUnitCore.java:44)
    Caused by: java.lang.ClassNotFoundException: oracle.jbo.ApplicationModule
            at java.net.URLClassLoader$1.run(Unknown Source)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.net.URLClassLoader.findClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
            at java.lang.ClassLoader.loadClass(Unknown Source)
            ... 27 more
    The Test project jar is created as ADF Library JAR File with Model.jpr as the dependent project. This takes care of project class dependencies
    All the adf library dependencies are added to the manifest file of the Test Project jar referring to a location lib/ in the jar file directory.
    I tried creating the ApplicationModule using both Configuration class (Configuration.createRootApplicationModule) as well as using the JDBC Connection String but both fail when I run the test cases independently from jmeter.
    Anybody came across such an error? Please help.
    Thanks,
    Sapna

    Hi Timo,
    Im using JDev version 11.1.1.6.0.
    I checked the class path on the jdev console. All the library references are mentioned in the manifest.mf classpath of the test project like below:
    Manifest-Version: 1.0
    Class-Path: lib/identitystore.jar
    lib/adfm.jar
    lib/groovy-all-1.6.3.jar
    lib/adftransactionsdt.jar
    lib/adf-dt-at-rt.jar
    lib/adfdt_common.jar
    lib/adflibrary.jar
    lib/xmlparserv2.jar
    lib/db-ca.jar
    lib/jdev-cm.jar
    lib/ojmisc.jar
    lib/commons-el.jar
    lib/jsp-el-api.jar
    etc...
    So I expect the library references should be resolved looking at the manifest file.
    Another set of entries that I see in the jdev classpath are related to the Model project which is under test.
    -classpath
    D:\CurrentProject_1\16_7_2013_3pm\11_7_2013\.adf;
    D:\CurrentProject_1\16_7_2013_3pm\11_7_2013\Model\classes;
    How do I put these entries into my class path? Will it be sufficient if I add the Model.jar into my test project classpath?
    Thanks,
    Sapna

  • Error when running VI to acquire data from multiple channels

    Hello there, I am currently trying to write a LabVIEW program interfacing with the Agilent 34970A data acquisition unit. Have managed to get seperate VIs to acquire temperature and voltage data and to graph the data. Running them separately is fine.
    However when I try run one after the other, (ie, run temperature acquisition VI, then voltage acquisition VI; or vice versa) the first one runs OK, but upon trying to run the second one I get a VISA error along the lines of "VISA write". When I try to run the first VI again, that one fails to acquire readings as well. Any way I can rectify this problem? (Want to combine the VI's into a single program.) Thanks!

    Hi Laeral:
    You should be able to just open one VISA session then write and read both commands then close the session at the end. This sounds to me like an error that comes from trying to open two VISA sessions to the instrument at the same time. I have attached some very basic LabVIEW VISA code that writes and reads two different commands. Hopefully it will get you started.
    Regards,
    Emilie S.
    Applications Engineer
    National Instruments
    Attachments:
    Basic VISA Example Two Commands.vi ‏39 KB

  • Error when running package to load data from InfoProvider

    I encounter the following error when using the standard package to load data from a InfoProvider to BPC. I tried loading the data from both DSO and InfoCube, but I get the same error.
    The log message where the error occurs is as follows:
    Task name CLEAR CUBE DATA:
    Could not perform write (INHERITED ERROR)
    The "convert" step of the process chain completed successfully. This error is happening when the "clear cube according data" step of the process chain gets executed.
    Any ideas on why this is happening?
    Thanks.

    Hi Laeral:
    You should be able to just open one VISA session then write and read both commands then close the session at the end. This sounds to me like an error that comes from trying to open two VISA sessions to the instrument at the same time. I have attached some very basic LabVIEW VISA code that writes and reads two different commands. Hopefully it will get you started.
    Regards,
    Emilie S.
    Applications Engineer
    National Instruments
    Attachments:
    Basic VISA Example Two Commands.vi ‏39 KB

  • Error in running Adobe forms inside Web DynPro in CE3

    Hi
    I have used Adobe Interactive form in a Web DynPro DC after doing the necessary configuration for ADS in CE SP3. But when I run the application I receive an exception somethis like this
    com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Interactive Form Operation Failed
    Caused by: com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process RenderRequest...
         at com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
         at com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:89)
         at com.sap.tc.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:112)
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:567)
         ... 61 more
    Caused by: com.sap.tc.adobe.pdfobject.core.PDFObjectRuntimeException: Processing exception during a "UsageRights" operation.
    Request start time: Wed Feb 27 19:55:39 IST 2008
    com.adobe.ProcessingException: Credential login error while applying usage rights to PDF: /usr/sap/CE1/J01/j2ee/cluster/server0/temp/adobewa_CE1_18726550/DM-6001642253044533767.dir/DM-5495524542707707125.tmp
    Specific error information:
    error while logging into credential ^0
    GeneralError: Operation failed.
    SecurityHandler.login:-1:
    Non-empty file name required
    Caused by: com.adobe.document.pdf.CredentialLoginFailure: IDL:com/adobe/document/pdf/CredentialLoginFailure:1.0.
    I have done all the configuration by following the blog in
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/7290. [original link is broken] [original link is broken] [original link is broken]
    Below file has been used for installing ADS credential
    P12 File: 20070730_0004205_P14.pfx
    Also the server has been restarted after all the configurations are done.
    What would be required more to overcome this error.
    Thanks & Regards
    Sudip

    Hello,
    are you sue the Alias name for the credential is exactly:
    ReaderRights
    What OS do you have?
    Regards,
    Dezso

  • Error when running the OWB process flow from the shell script

    Hi,
    I am able to deploy the process flow succesfully but when I execute the process flow from the shell script,I am getting the following error.Previously it worked fine.
    I had to make some chnage in the IP address,so i had to deploy again.
    Connected.
    SQL> @/oracle/product/owb92028/owb/rtp/sql/oem_exec_template.sql OWB_RTR LOC_P_REL PROCESS P_W_SOURCE "," ","
    Elapsed: 00:00:00.00
    Elapsed: 00:00:00.01
    Stage 1: Decoding Parameters
    | location_name=LOC_P_REL
    | task_type=ProcessFlow
    | task_name=P_W_SOURCE
    Stage 2: Opening Task
    declare
    ERROR at line 1:
    ORA-01422: exact fetch returns more than requested number of rows
    ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 17
    ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 137
    ORA-06512: at "OWB_RTR.WB_RT_API_EXEC", line 164
    ORA-06512: at line 205
    Thanks in advance.
    Vinay

    Hi Kamal and kanakam kolla,
    This is just to let you know that,I solved my problem little differently by creating a new location and deployed the process flow.Now my process flow is working fine when i call from the shell script.What i see is that, it does not update properly when we update and redeploy the process flow.So far this is the work arround i could think off and i succesfully tested this.
    Thank you Kamal and kanakam kolla,for giving a thought towards my problem.
    Thanks
    Vinay

  • Syntax error when running ActionFileToXML.jsx or trying to install xtools

    I have an action set (actually a few) that I would REALLY love to rename but the actions are calling "sub" actions within the action set which means that the action set name is hard-coded into the actions in many places.
    Originally, I tried to edit my actions with a hex editor to try and change the name and references but realised I was limited to renaming with the same number of characters unless I parsed the file first... so I gave up on that. Then I came across Xbytor's awesome ActionFileToXML script, but I get a syntax error when running both the To and From XML scripts at root.@date = Stdlib.toISODateString();
    I then figured I would go straight for the latest xtools instead but when running the install (in CS2) I get a rather long syntax error and so the install fails. The script mentioned that there is a log file that I should email to Xbytor, but I figured I would post here instead of bothering him directly so he has more of a choice about whether he wants to be bothered by me Or maybe someone else can answer if it is a stupid newbie problem.
    Thanks heaps!
    Gab
    ETA: I'm running CS2 on XP if that makes any difference. If so, I may be able to use a friend's Mac with CS3.

    Thanks for the quick (and very useful) response!
    I made the changes to the mentioned files and the scripts were able to
    progress further, but only until the next E4X syntax (node.@key=key;).
    Rather than continue to hack at your code, I figured I should downgrade to a
    previous version (as you also suggested).  I initially tried v1.5 and the
    ActionFileToXML worked perfectly but ActionFileFromXML failed with an
    illegal argument error.
    Before looking too deeply into the error, I figured I would try v1.6 and
    found that both the scripts were able to complete successfully. The
    resulting atn file has a couple of bugs in it (such as "Set current layer"
    having a knockout setting of  which causes the action to crash),
    but nothing that I can't just copy back from my original script.
    Thanks HEAPS for your assistance and for the awesome scripts in the first
    place! Extremely greatly appreciated!

  • Fatal region error detected; run  Recovery

    I try include 2600 documents 1,06 GB and I have the message (Fatal region error detected; run Recovery ). I executed db_recover.exe to try resolve the problem without sucess. I did this test in 3 differents computers and I had the same problem. I am use a free version , I am studyng berkeley db xml and need test performance with a big collection of document xml. Why am I have problem if berkeley db xml is able to support terabyte in size.

    This message indicates that you are probably setting your Berkeley DB cache size too large. MapViewOfFile is the Windows API used to map the cache file. It will fail if Windows cannot find enough contiguous VM for the mapping.
    Regards,
    George
    I have about 30 documents ~10MB and I get this all
    the time.
    MapViewOfFile: Not enough storage is available to
    process this command.
    PANIC: Not enough space
    com.sleepycat.db.RunRecoveryException:
    DB_RUNRECOVERY: Fatal error, run database recovery:
    DB_RUNRECOVERY: Fatal error, run database recovery
    at
    t
    com.sleepycat.db.internal.db_javaJNI.DbEnv_open(Native
    Method)
    at
    t
    com.sleepycat.db.internal.DbEnv.open(DbEnv.java:262)
    at
    t
    com.sleepycat.db.EnvironmentConfig.openEnvironment(Env
    ironmentConfig.java:908)
    at
    t
    com.sleepycat.db.Environment.<init>(Environment.java:3
    0
    This is under WinXP with BDXML 2.3.10.

  • Dynamically called VI becomes broken inside an executable. Error 1003 from "Open VI Reference".

    Here's the problem. Dynamically called VI becomes broken inside an executable in debug executable mode Error 1003 is occuring from "Open VI Reference" Block. The computer has all of the necessary drivers, NI-VISA and NI-DAQmx. This executable is a new release of software that currently works on the PC in question. I can using NI-VISA Remote Server control the instruments from my PC using the executable. But when I put the executable on the PC I am getting this error. The only way I have been able to get this to work properly is to build the executable from the console I believe the project was created in, note that the project file has been moved to a network drive and it still works. All of the stations I have opened the project in show the VI that is being called is runnable. I've tried building the executable from the console I am deploying to and the same thing happens.
    I am honestly at a loss for ideas why this is occuring. Is this something about the way LabView works internally that may be causing this problem?
    I have trolled this forum for idea's and none have made sense to me.
    Any input would be greatly appreciated.
    -Nate

    Two ideas:
    Mass compile the project to ensure all linkages are ironed out
    Include the dynamically launched VI's into the "Always Included" section of the build spec
    Report back on if either of these actions solves your problem.
    a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

  • Calling subvis dynamicall​y from within an exe (avoiding error 1003)

    Hi,
    I'm using an architecture where the main program (compiled to an exe) can be supplied with user-"plugins" that are collections of vis of specific types inside a specially named folder relative to the exe. They can be called from within the exe via "open vi reference" supplied by the corresponding strict vi types and the corresponding relative paths.
    I want to avoid having to include any of the plugins in any way in the application builder, since users should be able to create own plugins that the application is totally unaware of during build.
    In principle this approach works quite well, since these plugins are not extremely complex, but occasionally I get an error 1003 when loading a plugin.
    I've read many old posts about this error in this particular situation, mostly using LV versions 7 or 8 (I'm using 2012). One suggestion was to build a source distribution for every plugin, including everything that is used from vi.lib, instr.lib, and user.lib. This indeed helped in my particular case - however, it bloats the plugin "distribution" (which consists originally only of a couple of user vis) extremely and makes user-side developement more complicated.
    Now some plugins run nicely from within the exe without having to build a source distribution for them (they still use many vi.lib vis) while others don't and I have no clue why...
    These plugins are wrappers for hardware drivers which allow controlling any hardware instrument from within the main application through a certain API. So, in a particular case, a plugin which produced error 1003 is using VISA serial functions (all inside ...\vi.lib\Instr\_visa.llb) and one without error doesn't (yet it uses many functions from ...\vi.lib\Utility\...).
    I can fix the VISA-problem in a simple way by including (only) the used VISA-vis (and typedefs) inside the plugin's folder and explicitely link to them (i.e. replace the VISA-vis from vi.lib with the copied ones in the plugin's folder - I guess this is also what the source distribution does).
    However, I'm confused why some plugins with linked vi.lib vis work while others produce an error 1003 unless those particular vis are explicitely distributed and linked with them...
    Oh and just for completeness: All plugins work fine if called from within the developement system, the problem occurs only if called from within an exe.
    Solved!
    Go to Solution.

    There are some VIs in vi.lib that call other VIs dynamically.  Sometimes you have to explicitly add these to the EXE or distribution.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • 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

  • Error 1003 after i upgrade from office 2000 to 2003

    I just now upgraded form MSOffice 2000 to MSOffice 2003. When I tried to rebuild my app using application builder I get an error 1003 c:\...\internal.llb\excel_save_workbook.vi. Possible reasons: The vi is not executable. I have completely uninstalled and reinstalled office and I have copied the toolkit's files to the harddrive and reinstalled the report generation toolkit from there, according to some of the help files in the knowledge base. Neither worked, although the original error was in _exceldynamicvis.vi and now its in the one mentioned above. nothing else has changed on the system. I can recompile my entire program using ctrl-shift and pressing the arrow at the same time, and there are no problems. Any help would be appreciated.
    -Mike

    Hi Mike,
    Try opening the “excel_save_workbook.vi” and see if there is a broken run arrow in that VI. Hopefully there is. You can then identify the exact node (it will be some invoke node or property node) that will be set to some function or property that is no longer valid in the new Office 2003 API.
    The issue here is that upgrading office causes changes in the office API that break other applications that call methods or properties of the old office API. You’ll just have to manually go in and reset the function call to the new function call in each of the VIs to update them with the new office 2003 API.
    Hope this helps. Good luck!
    Kileen

  • 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 when running .exe

    I am having a problem with error 1003 when I run a built application.  I have searched the forums and found many others with this problem, but they encounter the problem while building the application, not while running the built .exe.
    I have a top level VI (AutoRun.vi) that calls 3 VIs in sequence.  All three are called in the same manner.  The first two work fine, but I get this error with the third sub vi.  This is how I call the subvi:
    Use App.kind, check for "Run Time System" (strip app path twice), or "Development System" (strip app path once)
    Build path to combine stripped path and file name of subvi to open
    open vi reference
    Invokee Node - Open FP
             Activated - T
             State - Standard
    Invoke Node - Run VI
              Wait until done - T
              Dispose ReF - F
    Invoke Node - Close FP
    Close VI Reference
    The error I get is:
    Error 1003 occurred at Invoke Node in AutoRun.vi
    Possible reasons:
    LabView: the VI is not executable
    I do not get this error while running in the development environment.  Only when I run it as a .exe.  Also I have had no problems with this code in the past.  I just made a small change and now I have this problem.  I have gone back to the old code and have the problem with it too. 
    I build the app by starting the app builder, selecting the top level VI, adding dynamic VIs and select all 3 subvis.  The front panel of the second VI is not visible while running.  I have to go in and manualy change the "Remove Panel" in the build settings for this VI from the default yes to no.  If I do not do this I get an error while trying to run the built application.  I have no idea why this happens either, but making this change fixes the problem.  After this I select build.
    BTW, I have LabView 7.0

    Hello,
    Not sure what happened on your end, but if the problem comes back repost and we'll explore it!
    Best Regards,
    JLS
    Best,
    JLS
    Sixclear

  • Error 1003 when loading a VI dynamically on LabView Run-time ini file configuration

    hi all,
    I have a problem with my runtime excutable.
    On 4 systems, all running XP it runs fine.
    On 2 systems ( one a new install of just LVRT 2011 SP1 ) I have:
    Error 1003 when loading a VI dynamically on LabView Real-time
    Or more spoecifically the error code is 1003 and the error source is Open VI Reference.
    When the RT app runs correctly I get these paths:
    Path Sent to Open Vi Reference:              Yeast_Grower.exe\Tecan_talk_Control.vi, 
    Path Returned from Open Vi Refence:       C:\Program Files\Yeast_Grower\Yeast_Grower.exe\Tecan_talk_Control.vi, 
    On a system that does gets the 1003 Open Vi Refence error I have the same Path Sent but of course no path returned as it does not open.
    To be sure that the vi Dyanmically called vi is compiled and valid at runtime I also include a copy of in the main.vi.
    To be extra sure I have also installed the runtime versions of VISA and DAQmx.
    I have compiled it with and without the "Use LV 8 calling hiaracy"
    My conclusion as this stage is that either the installation of LVRT 2011SP1 misses something the earlier LVRT installtions make.
    or is there a MyApp.ini or LVRT .ini  that controls how the RT dyanim calls are handled.
    Help very welcome how to solve this puzzle.
    thanks
    michael

    I understand that all the PCs (6 of them) have LV 2011 SP1, runtime or the development system installed. Right?
    How many of these PCs have the source code available on them?
    -> Only one of them has the source code.
    I am not sure I understood 'I also include a copy of in the main.vi'. Does it mean you placed the subvi in the main.vi?
    -> I meant I have included in main.vi the actual vi that is called dynamically - but only where it is not called.
    Did you try including the sub vi which is called dynamically, as 'Always included' in the EXE build?
    -> No, I did not know of this option - but the above I did this by default.
    Edit: Did you verify the software versions of LV RT, VISA etc on all the PCs? Are they same?
    -> I did verify even added DAQmx just in case
    There is lots of material available on this forum for error 1003 and dynamic vi calling. Did you find anything useful to try among the forums threads?
    -> I did view many of them.
    I did finally find the answer.  
    I have a subvi (callNet.vi ) in the dynamically called vi (dynamic ) that calls .Net libraries.
    Now the thing is that this subvi callNet.vi is coded out by enclosing it in a Disable structure.
    In fact this subvi ( callNet.vi) does not even compile - ie it has a broken arrow
    however if enclosed in a Disabled structure and disabled, the enclosing vi compiles OK.
    However I have discovered that even with the .Net calling subvi (callNet.vi) in the Disabled state of the Disabled structure
    the enclosing vi (dynamic.vi ) does NOT run - although it compiles just fine.
    Once I installed the .Net libraries (I actually did include them with my app installer ) with the vender's supplied installer
    then my app now successfully calls the dynamic vi.
    So the Summary and warning is:  Even if the dynamic called vi is included in Main.vi and Main.exe runs ( but does not call the dynamic vi - except when called dynamically at later some point ) and even if, in this case, the .Net calling subvi is disabled out ie no .Net calls are made the dynamically called vi will not run when called dynamically.
    I hope that is not too confusing.  In summary it seems the Disable structure does not entirely disable.
    Michael

Maybe you are looking for