Mass Compiler Error 13

Hello,
We are mass compiling a solution on client machines. To do this we just select the current base directory and hit mass compiler. There are dll's, vi's and vit's in various subfolders that we need processed. This all seems to work fine, but we are getting the following error:
#### Starting Mass Compile: Fri, Apr 07, 2006 5:28:42 PM
  Directory: "C:\TOMVIEW"
CompileFolder: error 13 at C:\TOMVIEW\dll\gateway.dll
CompileFolder: error 13 at C:\TOMVIEW\dll\gatewayfc.dll
CompileFolder: error 13 at C:\TOMVIEW\dll\gatewaygJ.dll
#### Finished Mass Compile: Fri, Apr 07, 2006 5:30:06 PM  
The folder dll contains 28 different dll's (that are all referenced from various VI's).
Question 1: Why is it doing anything at all with these dll's?
Question 2: How can we prevent this error from occuring (it does not seem to have an effect anyway)?
Question 3: Do we have a problem at all?
Best wishes, Marcus
Tomlab Optimization Inc.
http://tomlab.biz
[email protected]
Marcus M. Edvall
Tomlab Optimization Inc.
855 Beech St #121
San Diego, CA 92101-2886
USA
web: http://tomopt.com
e-mail: [email protected]
Office1: (619) 203-2037
Office2: (619) 595-0472
Fax: (619) 245-2476

Hi Marcus
The easiest solution is to move these dll's to another directory, next to the math compile path.
The second best option is the filtering of the messages.
The best solution is that someone within NI fixes this e.g. by giving you the opportunity to accept mass compile errors of a certain kind.
At last somebody can write a new mass compile for you.
In fact it is nothing more than traversing the directory tree and trying to compile each vi.
I hope somebody that has the time and knowledge to help you will pick this up.
greetings from the Netherlands

Similar Messages

  • Mass Compile "Bad VI" & "Bad SubVI" errors, but with no apparent errors.

    I am using LabView 8.5, FIRST Robotics Competition Edition, targeting the Compact RIO.
    I am getting Mass Compile "Bad VI" & "Bad SubVi" Errors, in my own code, but with no apparent errors in the vi's themselves.
     #### Starting Mass Compile: Mon, Jan 19, 2009 11:59:34 PM
      Directory: "C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Robot.lvproj"
      ### Bad VI:    "Autonomous Independent.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Autonomous Independent.vi"
      ### Bad VI:    "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"
      ### Bad subVI: "CrazyIvan.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\CrazyIvan.vi"
      ### Bad subVI: "Teleop.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Teleop.vi"
      ### Bad VI:    "Autonomous Independent.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Autonomous Independent.vi"
      ### Bad VI:    "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"
      ### Bad subVI: "CrazyIvan.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\CrazyIvan.vi"
      ### Bad VI:    "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"
      ### Bad VI:    "Autonomous Independent.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Autonomous Independent.vi"
      ### Bad VI:    "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"aa
      ### Bad subVI: "CrazyIvan.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\CrazyIvan.vi"
      ### Bad subVI: "Teleop.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Teleop.vi"
      ### Bad subVI: "Robot Main.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Robot Main.vi"
    #### Finished Mass Compile: Mon, Jan 19, 2009 11:59:46 PM
    Since some of these reference each other, this is the block diagram of one that doesn't reference any other erroring vi's.
    What can I do to fix this?
    Attachments:
    BlockDiagram.png ‏29 KB

    Interesting... It must have timed out before the temporary image did, and so I did not noticed a problem until I returned.
    Regardlessly, I have found the error.
    Errors did exist in my VI's, In particular, one of the subVi's I called in the VI shown happened to be private only, and so couldn't be used -- now I've just made a public version for my personal use. But LabView would not show me the actual errors unless I force-ran the the program, I really don't know why I had to do this, but when I did, it showed me a nice little dialog with my errors in it.
    I am confused, as when I did normal runs, it would simply complain that the VI's were invalid and would not permit the run.
    Very odd. 

  • "red X" error during mass-compiling installing labview upgrade 6.0.2

    I always get a "red X" error during installation of the LabVIEW 6.0.2 upgrade.
    The mass compiling always fails.
    The environnement is an italian version of W98.
    Salvatore Randazzo
    [email protected]

    I would try compiling one directory or .llb at a time instead. See if you can isolate the problem.

  • LabVIEW classes and mass compile

    Just wondering if anyone out there has found any problems mass compiling LabVIEW classes, as I am having what appears to be totally un-resolvable issues - I get a list of VIs that either say BadsubVI or BadVI all of which I have verified are error free.
    The only thing I can round it down to is the use of the lvclasses, and in particular the fact that I'm making extensive use of the inheritance functionality, and also a few override vi's.
    It wouldn't be such an issue except that I'm calling some of these vi's from TestStand, and am unable to get a deployment to work without a successful mass compile.
    Appreciate any responses,
    David Clark
    CLA | CTA
    CLA Design Ltd
    Hampshire, England

    I'm not sure if it's the same problem but I had a vi that would compile into an unrunable exe. I found the problem by mass compiling the project, which came up with a bad vi and bad subvi's that used that vi. Turns out my problem was that I had two classes with the same name (even though they were in separate lvlibs). And renaming one corrected my problem. LabVIEW 8.5 gives a warning and renames the compiled vi's (so if you could try 8.5, that might help you find the problem quicker assuming it's related). It seems to me that the name spaces provided by lvlibs go away when compiled into an exe or by the mass compiler (It may just affect lvlclasses).
    Matt

  • Mass compile in Windows 7 on SimpleErrorHandler.vi

    Hello,
    i wrote some action in Labview 2011 that i want to use in Teststand with labview-runtime.
    But some of them are not working and cant be loaded in Teststand. So someone told me to run a mass-compile.
    I did this several times (also on complete drive c but with no luck.
    Now i found out that only the vis that are using the "Simple-Error-handler.vi" are not working and cant be loaded.
    When i delete this vi from my VIs then i have no problems any more.
    So i opened the SimpleErrorHandler.vi manually in Labview and selected "Save All".
    Then i get a popup:
    Cannot save VI "FXP.xctl:fxpInit.vi"
    The VI already exists and you do not have permission to replace it."
    How can i resave it? I think the SimpleErrorHAndler must be also saved in Labview 2011 to be runable in the runtime2011
    Thanks for help

    Just to close the Circle:
    This Thread deals with the same Problem:
    http://forums.ni.com/t5/NI-TestStand/Vi-not-running-when-using-NI-s-SiimpleErrorHandler-vi-TS2010/m-...
    Regards!
    Moritz M.

  • Compiler error

    Two compiler error occurred when I progromed with LabView 6i to implement serial communication.
    "copy cvt, csrc=ox40"
    "bad mode in _GenCopyNumCod xc=0x40"
    Why? Thanx.

    Hello,
    I know that several 'compiler errors' were fixed in the LabVIEW 6.0.2 update. You can download this update from the NI website. After installing the update I recommend you perform a mass compile of your VIs. You can learn more about mass compiling in the LabVIEW on-line help.
    If after mass compiling in LabVIEW 6.0.2 you are still having problems, please let me know...if possible, please attach a simple VI that demonstrates the problem.
    Have a pleasant day.
    Darren N.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • LV 2011 (and LV 2012) Compiler Error. Invalid size in _InstSize: 21

    I created a subvi in LV8.5 to handle user interface events outside a main vi. The subvi gets the control references which are registered for events, by a queue all actions are sent to a consumer case, nothing fancy. Everything works fine in LV8.5, but now I took all over to LV2011SP1 on a Windows 7 64bit and I get always the same error:
    "Compiler error. Report this problem to National Instruments Tech Support. Invalid size in _InstSize 21"
    that pops up 3 times. I tried to open the same code also in LV2012, same error... When trying to isolate the problem, I found out that by disabling code in the 3 biggest consumer cases I can get rid of the warning, but then I can't reduce the problem to one single element...
    Any ideas? 
    Solved!
    Go to Solution.
    Attachments:
    Compiler error. Invalid size in _InstSize 21.png ‏7 KB

    DavidZ. wrote:
    I created a subvi in LV8.5 to handle user interface events outside a main vi. The subvi gets the control references which are registered for events, by a queue all actions are sent to a consumer case, nothing fancy. Everything works fine in LV8.5, but now I took all over to LV2011SP1 on a Windows 7 64bit and I get always the same error:
    "Compiler error. Report this problem to National Instruments Tech Support. Invalid size in _InstSize 21"
    that pops up 3 times. I tried to open the same code also in LV2012, same error... When trying to isolate the problem, I found out that by disabling code in the 3 biggest consumer cases I can get rid of the warning, but then I can't reduce the problem to one single element...
    Any ideas? 
    Try to inline the subvi's.
    Try making them reentrant.
    Mass compile.
    Press ctrl-shift-arrow to force recompile of the entire vi call hierarchy.
    Try separating the source from the binary.
    Br,
    /Roger

  • LabVIEW crashes during mass compilation every time

    Hello All
    I have installed a new LabVIEW 7.1 from February on Win XP.
    Every time when I try to mass compile LabVIEW, after few files it crashes, and only one thing I can do is to send a report to Microsoft.
    It looks like it crashes in a moment when it can not find a subvi in the directory structure.
    What is wrong with it?
    Thanks in advance.
    Pawel

    I hope you are not trying to mass compile the entire LabVIEW directory. I will definately choke on several of the files it will find. If you have upgraded to 7.1.1, you should mass compile the vi.lib, instr.lib, user.lib and examples directories.
    You could also have an error with the Paths settings. If it is searching an invalid path to find a subvi, that might cause the problem.
    I suggest that you start small and try a single subdirectory like user.lib, then move on to instr.lib, then examples.
    Michael Munroe, ABCDEF
    Certified LabVIEW Developer, MCP
    Find and fix bad VI Properties with Property Inspector

  • Mass compile dialog after saving vi's on Perforce

    I have been receiving errors saving vi's to Perforce which prompted a mass compile.  Upon completion, I received the attached dialog box.  Can anyone give me direction/suggestions how to proceed?
    Thank you.
    Attachments:
    MassCompile09Aug2013.txt ‏551 KB

    It appears that LabVIEW is having trouble locating the Visa.  When performing the mass compile do you have access to edit all the Visa and sub Visa that it is trying to access?  Also, you could also try saving the project onto your desktop with all the files, mass compiling, and then individually moving them into Perforce but that would be tedious.
    Jesse S.
    Applications Engineer
    National Instruments

  • Mass compile / defer decision

    When trying to do a deployment in TestStand I got errors about changed VIs that weren't saved. They weren't saved because I didn't want to save the changes and TestStand crashed (again). Searching the TestStand forum it seems I need to perform a mass compile. If a mass compile is done what is compiled, the original version or the changes I did not want to save?
    Is there any chance that NI will change this maddening feature to allow quitting without saving  or deferring?
    thanks,
    jvh 

    jvh,
    The reason that it is asking you to save is because the deployment utility is making modifications to your VIs and their sub-VIs to make sure everything is in a compatible version for deployment.  What are your adapter settings on this development machine? (using LabVIEW RTE or LabVIEW development system?)
    What VIs are the utility asking you to save?  If we know that, we can better figure out why changes are being made to these VIs and give a recommendation on whether or not it's ok to just save the changes to make everything work as expected.
    Eric B.
    National Instruments

  • Mass compile operation keeps on looping

    hi,
    when i do  a mass compile on my  project ,  it keeps on looping  during a save operation
    and it does that may be a 50 times & eventually  ends also without error.
    the curent file remains the same
    Attachments:
    mass-compile-loop.PNG ‏15 KB

    Just as TiTou said: it looks like recompiling each VI which depend on any class hierarchy makes LV recompile each VI of this hierarchy, and then each VI of this class makes recompilation of each other VI, etc... As a workaround you can try closing the project and mass compile project folder from Tools->Advanced menu. I noticed this does not loop as much as there are not all dependencies loaded, but there are many more factors to this (i.e. how you managed libraries and classes dependencies). Furthermore, this might not give you exactly the same effect as mass compiling the project (same reason - not all dependencies are loaded).

  • Difference between Mass compile in Project %26 in LabviewTools Advanced mass Compile

    what is the differece betwen the two,  Mass Compile option in a Project(LVPROJ) and  LabviewTools Advanced mass Compile
    The Issue is if I do the Mass compile thr' the Project I do not get an Error.
    But if I  mass compile thr' labview >> tools>> adv. Settings>>mass compile  it shows BAD VI ??
     

     
    My Project folder is clear of   Erorr VIs  -->>  there are none
    inspite of that  the difference exist.
    I am using classes in my Project &   may be  the   class contains information abt  the VIs (the broken ones) 
    My Class is added ina llb file which is  part of my project...
    In runtine I get issues  with the project.

  • Problems with mass compiling for LabVIEW 6.0.2

    When mass compiling the LabVIEW folder after installing 6.0.2, I get a Log file telling me "Bad VI" for 8866 vi:s. Have looked specifically at two of them, and the broken arrows are fixed by pressing and clicking the broken arrow. Somehow I don't feel like doing this for 8866 vi:s.
    What is wrong, and how do I fix it?
    Attaching the Log.
    //Martin
    Attachments:
    MassCompileLog ‏1263 KB

    Yes, it definitely appears as though you need to reinstall NI-DAQ. You can receive this error when the VIs which are being mass compiled depend upon other VIs which are either not present or have been incorrectly updated. Make sure that you have installed NI-DAQ support for your new version of LabVIEW. This is separate from installed NI-DAQ by itself. You must install the LabVIEW support files also. You can get these off of NI's website.
    Also, if you did a complete install of LabVIEW, you may have installed a newer version of NI-DAQ without realizing it. This could cause a problem if there are two versions of NI-DAQ on your computer. Make sure you only have one version.
    J.R. Allen

  • Compilation error while calling static method from another class

    Hi,
    I am new to Java Programming. I have written two class files Dummy1 and Dummy2.java in the same package Test.
    In Dummy1.java I have declared a static final variable and a static method as you can see it below.
    package Test;
    import java.io.*;
    public class Dummy1
    public static final int var1= 10;
    public static int varDisp(int var2)
    return(var1+var2);
    This is program is compiling fine.
    I have called the static method varDisp from the class Dummy2 and it is as follows
    package Test;
    import java.io.*;
    public class Dummy2
    public int var3=15;
    public int test=0;
    test+=Dummy1.varDisp(var3);
    and when i compile Dummy2.java, there is a compilation error <identifier > expected.
    Please help me in this program.

    public class Dummy2
    public int var3=15;
    public int test=0;
    test+=Dummy1.varDisp(var3);
    }test+=Dummy1.varDisplay(var3);
    must be in a method, it cannot just be out somewhere in the class!

  • Compile Error: "schema 'name' does not exist

    Im trying to build a program that quereys a table in a database but i keep getting this error. Am i missing a link between the files or am i missing a line of code in my program??

    Apologies. I receive a compiler error which reads as follows;
    java.lang.ClassNotFoundException: org.apache.derby.jdbc.EmbeddedDriver
    java.sql.SQLSyntaxErrorException: Schema 'DEMO' does not exist
    Heres the main body of code i am trying to execute.
    public class Main {
    * @param args the command line arguments
    public static void main(String[] args) {
    // TODO code application logic here
    try{
    Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
    }catch(ClassNotFoundException e){
    System.out.println(e);
    try{
    Connection con = DriverManager.getConnection("jdbc:derby://localhost:1527/SimpleDBDemo", "demo", "demo");
    Statement stmt = con.createStatement();
    ResultSet rs = stmt.executeQuery("SELECT * FROM DEMO.Table1");
    while (rs.next()) {
    String s = rs.getString("Name");
    float n = rs.getFloat("Age");
    System.out.println(s + " " + n);
    }catch(SQLException e){
    System.err.println(e);
    I am using NetBeans IDE and have created a database under: Services->Databases-> Java DB->SimpleDBDemo.
    I have a database connection in which theres a simple table (called "TABLE1") created which contains the names and ages of two people.
    Hope this makes the problem a bit clearer.
    Any help would be greatly appreciated.

Maybe you are looking for