Open Specific WorkBook.v​i: subVI is not executable error

Hi,
I'm trying to programaticaly change some cells of a specific worksheet and then saving it on a new file.
But I can't run the VI because I get the error Open Specific WorkBook.vi: subVI is not executable.
I've atteched a printscreen of my VI.
Any hints?
Daniel Coelho
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda
Solved!
Go to Solution.
Attachments:
VI.JPG ‏16 KB

This is the Open Specific WorkBook.vi with the error.
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda
Attachments:
VI2.JPG ‏140 KB

Similar Messages

  • Subvi is not executable error, but it has no error

    Hey I hope you can help me with a weird error.
    I got the error "SubVi  'name' : SubVi is not executable" but when I click on the SubVi and open it it does not show me any description of an error. If I open the main vi or the SubVi alone it shows no error. Could it be a problem of a library or something else?
    I am using Labview 2012 and Labview 2012 Mindstorms NXT.
    If you neew more screenshots or the rest of the SubVis please tell me so :-)
    Thank you!
    Jan
    Attachments:
    automatischer Modus - ohne Wait - ohne Array - global.vi ‏80 KB
    Solar.vi ‏15 KB
    project.png ‏262 KB

    SmartCity-Project wrote:
    Thanks for all your replies!
    I found the error, the NXT does not support global variables in Target on NXT- Mode so I changed to Target on Computer - Mode and now it works.
    Unfortunately the program crashes after 15 minutes more or less. Could you imagine why? Is it because of to many bluetooth connections or a bad programm structure?
    After a very quick look at the code I would say that it is probably bad code. Your overuse of global variables, sequence structures and silly things like a For loop set to run once with everything inside the loop wrapped in a sequence frame is a goo dindication that you need to learn much more about data flow programming techniques. With the amount of global variables you are using your program is probably ripe with race conditions. In addition, you did not include any of the subVIs so we cannot see what is happening in them.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • Tried the solutions posted for this "SubVI filter not executable​. Undefined error" but not solving the problem

    Hello,
    I am trying to use a lowpass filter for my application but getting the error "SubVI filter not executable. Undefined error".I tried working with the solutions at this post 
    http://forums.ni.com/t5/LabVIEW/SubVI-filter-not-e​xecutable-Undefined-error/m-p/1996701#M657751 and results with
    1. Create a blank vi, put a VI filter in the block diagram (this should not be functional as it is not wired), copy it and paste it in my other project. I believe if the filter is the first vi of a blank project, it is funcitonal and then you may copy it wherever you need to.
    Result:
    2.Tried to open the filter panel of the Filter but showing the same error as shown inthe below image
    Don't why the solutions worked for others are not working.Can someone suggest a solution for this.
    thanks in advance.

    Hi PatanGova,
    Very strange error. Actually, there are no required inputs on this express VI, so it should be able to run even without wires. It is not correct as you said: "this should not be functional as it is not wired". Nothing will happen, true, but the run arrow should not be broken.
    For some reason, the VI with the Filter express VI fails to compile. I tried it on my computer (LV 2013) and get no error when I add it to a new VI. As was suggested in the linked forum thread, you need to open the front panel of the Filter VI and run it to see the explicit error.
    If you do, do you also get the error:
    "This VI claims to be part of a library that does not include the VI. The VI might have been deleted from the library. Add the VI to the library again or select File - Disconnect from the library."?
    If you do, it seems that you may have a project library somewhere that has taken ownership of the express VI. The ownership prevents you from running or editing the express VI. To free the VI, you need to do one of two things. Either, you need to load the library into memory, or you need to disconnect the VI from the library. Either way, you need to find the project library that has taken the ownership of the VI. As soon as it is released, it should run for you. You release it by selecting File»Disconnect from Library on the VI.
    The workaround described in your link (and also here: http://forums.ni.com/t5/LabVIEW/compatibility-prob​lem-labview-2009-2010-2011-quot-This-VI-claims/td-​... tells that you can make a copy of the VI and thereby create another instance that is free. This solution may work for you as well, but if not, you may not have created the copy properly. Maybe your copy of the VI also became part of some project library that took ownership. In either way, you should rather find the project library to release the VI before trying the workaround to copy it.
    If project library ownership is not the problem, maybe the problem is connected to LV 2011, as most forum posters report that it only happens here.

  • Simulation interface toolkit: SUB VI not executable error

    Hi;
    I have a real-time application where I model things in Simulink and use Simulation Interface Toolkit to carry out hardware-in-the-loop simulations. As a real-time target, I am using NI-PXI8106 with NI-PXI6251 DAQ card on it. Up until now, I was able to run my code just fine. However, for some reason, my vi didn't work today and gave several errors such as:
    SubVI NI_SIT_sitclient.Lvlib:RVE.vi: SubVI is not executable
    Details:The SubVI is not executable. You must fix all error in the subVI before this VI can run.
    SubVI NI_SIT_sit Init Model.vi: SubVI is not executable
    Details:The SubVI is not executable. You must fix all error in the subVI before this VI can run.
    This is just few of many error that I received...In the details section of the error list window, the error statement are usually like the following:
    SUBVI not supported for current target..
    Type not supported in the current target...
    The only thing that changed since the last time I ran this program with success is the IP change of the target machine..However, when I use Measurement and Automation tool, I am able to access my target machine (PXI8106) without a problem...Maybe there are some certain rules for IP settings on the PXI target? ...I can provide the details of my new IP configuration numbers if necessary...
    I also  reinstalled the SIT 5.0 on the target machine but It didn't do the trick. I am wondering if there is anyone out there who can help me out with this problem..
    Thank you so much!
    Kind Regards.

    Hi there,
    I was just wondering if you did manage to solve this problem. I'm a new user and have recently started using the Simulation interface toolkit. I have created my model using Simulink and used the real-time workshop to convert it to a .dll file. I tried to run it on labview and it seems to build it on the realtime target, however as soon as map it to the hardware (using a NI BNC-2111,It's just a bunch of analog inputs and output which I have connected to a voltmeter), a dialog box pops up with the the following error:
    Error 1003 occurred during host VI initialization: SIT_test1.vi >> NI_SIT_sitclient.lvlib:sit Init Model.vi >> NI_SIT_sitclient.lvlib:sit Connect to Target.vi
    <append>=========================
    Simulation Interface Toolkit:  The driver VI (SIT_Test_Driver.vi) is not executable.
    Check the following:
    1) You have not modified the driver VI.
    2) You properly installed SIT and any necessary driver software on the target.
    3) The target has not been locked from Measurement and Automation Explorer.
    Do you want to launch the SIT Connection Manager dialog box and reconfigure the simulation?
    Please look at the JPEG picture attached below to see how the error looks on my monitor.
    Thanks
    Attachments:
    error1.JPG ‏135 KB

  • SubVI not executable error only when opening another VI in same instance of LabView

    I have a VI (ill refer to as "A")that I have written for some of my components of my system, one of them being a loop that polls a pump controller to pick up the data (pressure, volume, etc.) coming from the pump.  Now I have been able to get a VI (Ill refer to as "B")from that manufacturer that allows me to not only get the data, but write a command to my pump controller to control my pumps from labview.  So, my goal was to just open both VI's (A and B), "copy and paste" (from B to A)so to speak, so that I could have controls incorporated into my existing VI (A) that has the controls for the rest of my components.  However, when i open both VIs in the same instance of labview, i always get errors from the second VI that i open.  Keep in mind that when running just one VI in an instance of labview, it gives me no errors.  The furthest ive gotten was to open my "B" VI first, then open my "A" VI, in which the "A" VI only gives me "not an executable error"  After investigating the source of the error, it says that it's coming from the loop inside my "A" VI of which polls my pump controller to get the data.  So basically what im thinking is that the programming thinks that one VI is coming up with the data, and one is controlling it, so it gets confused as to whats actually going on. 
    Any help or suggestions would be greatly appreciated.  I can attach some of the VIs if need, figured Id try to get some ideas first as to maybe what is going on...
    Thanks in advance!
    Matt

    What errors?  Do they have an error number?  Do they have a description?
    Since you said communication, I'm going to assume that it is serial communication and is using VISA drivers.
    It is very likely the two VI's are stepping on each other's communication while they are trying to communicate with the pump.
    Why don't you post the two VI's so we can see what you are doing?

  • SubVI filter not executable. Undefined error.

    Good morning,
    During the development of a bigger labview project, I came to need filtering of my waveforms at some point. I am getting a broken arrow signaling the filter assistant :
    "SubVI 'Filter' : SuvVI is not executable"
    I thought it could have something to see with the whole program and thus created a simple VI of acquisition from a myDAQ aparatus and had the same error.
    Do you have any idea how I could at least identify the error?
    Thanks in advance,
    David

    David Pastorino wrote:
    Good morning,
    During the development of a bigger labview project, I came to need filtering of my waveforms at some point. I am getting a broken arrow signaling the filter assistant :
    "SubVI 'Filter' : SuvVI is not executable"
    I thought it could have something to see with the whole program and thus created a simple VI of acquisition from a myDAQ aparatus and had the same error.
    Do you have any idea how I could at least identify the error?
    Thanks in advance,
    David
    If you open the SubVI Filter and hit Ctrl+R LabVIEW should tell you what you need to fix in that VI.
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

  • Statement handle not executed error

    Hi,
    I have a package which have a statement as follows.
    OPEN p_out_provider_w_POSAccess FOR
                   SELECT DISTINCT claim.cert_no, claim.rec_code,
                                   prov.ghi_prov_num, prov.irs_number tax_id,
                                   prov.full_name, prov.lastname, prov.firstname
                              FROM hmo.hmo_medical_claim claim,
                                   ipd2.i_provider prov,
                                   ipd2.i_provider_top pt,
                                   ops_arw.phr_top top,
                                   ops_arw.provider_pin pin
                             WHERE claim.cert_no =hmo_conv_num_to_letter (p_in_cert_no)
                               AND claim.rec_code = p_in_rec_code
                               AND claim.ghi_prov_num = prov.ghi_prov_num
                               AND claim.ghi_prov_num = pt.ghi_prov_num
                               AND claim.ghi_prov_num = pin.ghi_prov_num
                               AND pt.top_code = top.top_code
                          ORDER BY prov.lastname, prov.firstname;                                
                                    when I execute the package ,I get
    dweb1:ops_arw> PRINT p_out_provider_w_POSAccess
    ERROR:
    ORA-24338: statement handle not executed
    SP2-0625: Error printing variable "p_out_provider_w_POSAccess"Thanks

    user11253970 wrote:
    No I am not closing it.Just now I noticed that when I input values which are in Database it returns the result without any failure.But when I try to input values which are not in database ,Instead of returning zero rows it gives the error message.Then your SP logic branches in such way that values which are not in the database bypass open cursor statement:
    SQL> create or replace
      2    procedure p1(p_cur in out sys_refcursor,p_ind number)
      3    is
      4    begin
      5        if p_ind = 1
      6          then
      7            open p_cur for select ename from emp where deptno = 10;
      8        end if;
      9  end;
    10  /
    Procedure created.
    SQL> exec p1(:p_cur,1)
    PL/SQL procedure successfully completed.
    SQL> print p_cur
    ENAME
    CLARK
    KING
    MILLER
    SQL> exec p1(:p_cur,0)
    PL/SQL procedure successfully completed.
    SQL> print p_cur
    ERROR:
    ORA-24338: statement handle not executed
    SP2-0625: Error printing variable "p_cur"
    SQL> SY.

  • App Builder produces "Not Executable" error with Strictly Typed VI Refs

    There is a very frustrating problem with the app builder in LV 8.0.1.  Certain VIs compile and run fine in labview, but the app builder
    refuses to make them into applications.
    The error message is very long and ends with something like "The VI is not
    executable".  Standard advice for this problem is to force LV to recompile
    everything you're building by either mass compiling or ctrl-shift clicking the
    run arrow, but this hasn't worked for me in two separate cases (completely
    different projects).
    It seems that this problem is caused by wiring a strictly typed VI reference to
    an invoke node with the FP.open method selected.  In both cases I resolved
    the issue by changing the Static VI Reference to be weakly typed (right-click
    the static vi reference and make sure "Strictly Typed VI Reference"
    is unchecked). After that, the project build successfully.
    This is very hard for a user to track down for several reasons:
     - The error message in the application builder does not give any
    indication as to what the real problem is
     - The app builder reports that the top-level VI is broken, even when the
    strictly typed reference and invoke node may occur in a sub VI
     - Nothing (that I can
    find at least) in the documentation suggests that strictly typed references
    won't work with the Open.FP method. 
    There is a page that says "some of the properties and methods do
    not work when you configure this function to output a strictly typed VI
    reference," but no indication is given of which methods fail
    Note that in one case I was also able to make the project
    build by deleting an instance of "IMAQ Create.vi" from the top-level
    VI.  I 
    have no explanation for this.
    Hopefully this post will save some other users the trouble
    of tracking this down and maybe even get NI to correct the issue for future
    versions.
    Adam Brewster

    Hello Adam,
    Thank you for sharing your experience and insight.  Your post was well thought-out and offered a
    good description of the problem as well as some possible workarounds.  I believe that the issue has been filed and
    is under investigation (3TU8T8V9).  Feel
    free to post back after the next LabVIEW release and inquire as to its status.
    Thanks again,  
    Travis M
    LabVIEW R&D
    National Instruments

  • I get a "vi is not executable" error when building an application.

    I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

    You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
    J.R. Allen

  • ORA-24338: statement handle not executed   -- error in returning refcursor

    My packaged procedure has Ref cursor as out variable.
    Calling the packaged procedure from Cognos 8. while trying to access the packaged procedure , getting the below error.
    ORA-24338: statement handle not executed
    Please provide a solution...

    Welcome to the forum!
    Whenever you post provide your 4 digit Oracle version (result of SELECT * FROM V$VERSION).
    Confirm that the procedure works properly when called from sql*plus.
    For example here is some code that tests a package procedure I have in the SCOTT schema
    SET SERVEROUTPUT ON SIZE 1000000
    DECLARE
      l_cursor  test_refcursor_pkg.my_ref_cursor;
      l_ename   emp.ename%TYPE;
      l_empno   emp.empno%TYPE;
    BEGIN
      test_refcursor_pkg.test_proc (l_cursor);
      LOOP
        FETCH l_cursor
        INTO  l_empno, l_ename;
        EXIT WHEN l_cursor%NOTFOUND;
        DBMS_OUTPUT.PUT_LINE(l_ename || ' | ' || l_empno);
      END LOOP;
      CLOSE l_cursor;
    END;
    /

  • Subvi is not executable

    labview 5.1
    Once copied my vi's from sol 2.6 machine to sol 2.8, problem is:
    "This Code Interface has no code to execute. Popup on it and select Load
    Object Code ...,
    then select the object code file (lsb)"
    In fact, it concerns all the cin nodes including the ones of labview...
    Saving development distribution by means of "Save with options" on 2.6
    and copying intro 2.8 doesn't help
    Thanks for ideas,
    Alexandre

    Hi Alexandre-
    I am a little confused to what is happening, are you able to popup and select the lsb file and it still doesn't work? Or is the lsb file not present?
    If the lsb file is no longer present, it probably got lost in your Operating System migration (2.6 -> 2.8)- you will just have to recompile your c code and recreate the object on the new system. This is not difficult and obviously you have achieved this already if your system was working properly. It does, however, require you to have the original source code which I really really hope you still have. If not, there is no present way of getting the source code from a compiled object - this "unfeature" is pretty standard in the CS field.
    If the tlb object does exist and you are in fact selecting the file
    and your vi is not acting like you expect, I would urge you to contact NI support and we can work through this together.
    I think recompiling is the way to go - moving compiled objects from one system to another reeks of potential problems.
    good luck, hope this helps-
    ben schulte
    national instruments

  • SubVI not executable: many express VIs cannot be opened

    When I create an icon of an express VI on the Block Diagram, "error loading National Instruments\LabVIEW 2012\resource\lvanlys.dll" appears. And when I double click the icon, it is shown on the screen "unable to view properties". I cannot run the VI, and the errors listed are like "SubVI 'simulate signal': SubVI is not executable". I do not know how to solve this problem.
    Hope someone can help me. Thanks a lot!

    What do you mean "create an icon of an express VI on the Block Diagram"?  Give us enough steps to be able to reproduce (or test) your problem.  Include:
    Are you starting with a "blank" VI or a blank Project, i.e. starting from scratch?
    What is on the Block Diagram before you "create the icon of an express VI"?
    Which Express VI are you trying to use?
    Lily092 wrote:
    When I create an icon of an express VI on the Block Diagram, "error loading National Instruments\LabVIEW 2012\resource\lvanlys.dll" appears. And when I double click the icon, it is shown on the screen "unable to view properties". I cannot run the VI, and the errors listed are like "SubVI 'simulate signal': SubVI is not executable". I do not know how to solve this problem.
    Hope someone can help me. Thanks a lot!

  • Help opening file - file not found error message

    When I try to open an excel file that shows up in the finder, excel opens but then I get a "file not found" error message.
    Any ideas what is going on?

    Hi Ceeblee,
    SOLVED
    How ?? This is a forum for sharing solving problems. So even you solved your own issue it would be helpful for others who read your topic to know how you solved. This could be helpful for future problems for other users.
    Thanks ...
    Dimaxum

  • .Not executable subVI

    Using LabView / fieldpoint with FP-1601, FP-TC-120 and FP-DO-410 I can use MAX to test the inputs and outputs, however when setting up any fieldpoint application in the labview window I get an error, of which states 'the subVI is not executable'.  I've checked and re checked but cannot seem to bypass this happenning.  There must be something small I'm not getting set up right.  Any ideas?  Thanks in advance.
    Steve
    Attachments:
    run1.vi ‏195 KB

    Hi Docbritzel
    Im not sure but maby this link will help you.
    regards
    Manuel

  • MS Office Report (Report Generation toolkit) is not executable​, Xnode broken?

    Hi, I am trying to generate an excel report, and I figured it would be easier to use the MS Office report VI, but I am getting the broken arrow saying the SubVI is not executable and that the library that defines the xnode is broken... here is a screensot attached, I already uninstall and reinstall the report generation toolkit and still the same... this is what I found on NI: "This error occurs when the library that defines the XNode you used is broken. To correct this error, reconfigure the XNode." but no idea how to reconfigure xnode
    Attachments:
    Error.png ‏67 KB

    What version of LabVIEW are you using?
    What is the nature of your Report?  What should it look like?  What kind of data should it contain?
    Can you show us some code that you've tried to use?  If so, include the code as either a Snippet or as a VI attachment (so we can plug it into our own LabVIEW installations and experiment with it).
    I generally find that the Report Generation Toolkit is a very easy way to generate Excel Workbooks.  I work primarily with LabVIEW 2012 and LabVIEW 2014.
    Bob Schor

Maybe you are looking for