Report Generation Toolkit missing VI

LabVIEW version 8.6.1
Report Generation Toolkit 1.13
I have just started work on an ongoing project that others have been contributing to for some time.  (Hence the project being in older versions of LabVIEW) 
On my PC, I am apparently missing the VI "Word Get ActiveX References.vi" 
I do have the version 1.13 of the toolkit installed, just as every other machine that runs this code does.  But my word.llb does not contain that VI
I have tried simply copying that VI into the .llb   The VI is then found by the application.  But is not executable due to this error:  This VI is connected with 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 Library.
I have also tried replacing my entire  C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\  directory with files from a PC that was working.  Again, I get the same error as above. 
I did attempt to do a repair on my installation of the toolkit.  But as far as I can tell, this didn't do anything.
I also tried simply reinstalling the toolkit.  But since it was already installed, it did nothing.  I am hesitant to uninstall and reinstall the toolkit for fear of breaking all of my 8.6 projects, as well as possibly my 2009 projects.  I wouldn't think it mess with my 2009 installation.  But I do know that the order in which things are installed can be critical in system with multiple versions.  I'm not sure if this applies to toolkits or not. 
This PC also has an installation of LV 2009 SP1, and that version also has the Report Generation Toolkit installed. (although it is a different revision of the toolkit than 1.13) 
I know that in the past, multiple versions of this toolkit were not compatible, meaning only one installed version of LabVIEW could have a working Report Generation Toolkit installed.  But I was of the understanding that this was no longer a problem.  Although it may not be a coincidence that neither of the other development boxes running this code do not have LV 2009 installed.  
Has anyone else ever run into a similar problem and found a solution? 
Thanks. 
Patrick Allen
Solved!
Go to Solution.

Darren wrote:
Back before we unified the LabVIEW and toolkit version numbers (in 2009), there were cases where we didn't change the version number in the registry for one reason or another on a minor upgrade.
Ah.  This makes sense then.  
I just reinstalled said toolkit from said SSP DVD and although it did tell me that I was about to install 1.1.4, MAX still thinks it's 1.1.3
...except that now I do have the missing VI.  This is a good thingTM
I still wonder how it ended up missing, because I'm really sure this is where I installed the toolkit from in the first place.   I'll probably never know for sure.  But that's a lot easier to take when the code is working.  
Thanks! 
Message Edited by pallen on 04-15-2010 04:52 PM
Patrick Allen

Similar Messages

  • Report Generation Toolkit Excel Vi's do not run after creating an executable​. What am I missing?

    I have labview 8.5 and Report Generation Toolkit version 1.1.2.   My vi works fine during development. When I make an executable or an installer the excel vi's do not work. I have seen this question posted before but it has always been for earlier revisions and the answers do not seem to apply with 8.5 and 1.1.2. 

    Hello ajh,
    You will have to include Dynamic VIs in the executable you build. The following link has more information:
    http://digital.ni.com/public.nsf/allkb/C38CE3F3054​2D65B86256F0E00740DD8
    Prashant.

  • Problem for Report Generation Toolkit for excel 2000

    Hi all,
    Now I am Developing my program with Report Generation Toolkit 1.1.0 and Labview 7.1.
    In my computer I am using Excel XP, and there is not any problem. But when I build to
    a exe file, and use in a computer with Excel 2000, it didn't work.
    And I try to check the source file in this computer, I found that there any some connection
    error. And this is caused by the active X class. As I know Excel 2000 is using Microsoft Excel
    Object Library 9.0, but i cannot find it in the list of active x. So it is using Microsoft Excel Object
    Library with a very old verison. So in the property node there are missing functions, such as the
    UsedRange in _Worksheet in the Excel_Get_Range.vi. However, In VBA, I can find the 9.0 Library.
    Is it the problem of 9.0 library? How can I solve the problem? How can I upgrade the library to 10.0?
    Thanks.
    Regard,
    Ryan

    Hi Mike,
    Since my program is for all the staff in office, everyone may use it.
    I cannot call the whole office to upgrade the excel to XP.
    And I think Report Generation Toolkit is alway support Excel 2000,
    since the old version of it is not support for Excel XP.
    Regard,
    Ryan

  • Problem building applicatio​n using Report Generation Toolkit, LV 2011

    I'm using LabVIEW 2011 under Windows 7.
    I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
    Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
    I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
    In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
    So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
    The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
    When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
    Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
    VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
    I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
    Thanks very much,
    mws
    Attachments:
    Test-App-Build.zip ‏336 KB

    Hi again,
    If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
    The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
    When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
    When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
    In the development environment, the whole thing runs with no problems.
    Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
    I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
    Thanks very much for any help!

  • Problem with Reporte Generation Toolkit for Microsoft Office 2010

    When I use the Report Generation Toolkit (LabVIEW 2010), and Office 2010,  the tables generated are bad.
    In office 2007 in the tables are correct.
    Someone can help me solve this problem?

    The solution referenced in your post does not actually workas far as I can tell... at least for LV2011 and Office2010 on Win7
    Am I missing something here?
    Attachments:
    Testbench_ReportGen Table_BUG.vi ‏10 KB

  • No Word or Excel selection in report generation toolkit

    I've uninstalled/repaired the Report Generation Toolkit that I received with 8.2 Toolkit disks. I still don't have the selection of Word or Excel with the New Report.vi.  All I get is Standard Report or HTML. Some magic I'm missing?
    PaulG.
    "I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

    Check out my reply (#4) in this thread, where I link to the KnowledgeBase entry that discusses having a toolkit installed to multiple LabVIEW versions.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Getting "Save File" permission message related to Report Generation Toolkit

    I started having this problem about a month ago.  It does not affect the operation of my project but is a minor nuisance, but a nuisance none the less.  I opened a couple of Excel Specific VIs.  I did not nor did I attempt to make any changes, I was just curious as to their content (truth is I wanted to see how the active X controls were being used).  Ever since then I get the attached messages when saving my project and have not been able to get rid of it.  When OK is pressed, a Save As dialog box appears (see attached) pointing to the NI directory which contains the Excel VIs for the Report Generation Toolkit.  I press cancel and am able to save my project VIs just fine, but I would like to get to the bottom of this problem.
    I would not think that simply opening a VI would cause this behavior.  I should also mention, it not only attempts to save the VIs I opened, but every RGT VI that is a part of my project, which is even stranger.  I have not attempted a reinstall.  I was hoping for something a little less drastic, and that won't prevent this from happening again, unless I can kill my curiousity that is. Is there a setting somewhere which I am missing?  Thanks in advance for your assistance.
    Reese
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home
    Attachments:
    Save Message.JPG ‏249 KB
    Save As Dialog box.JPG ‏305 KB

    It did not work.  In fact, it called out four bad VIs (see attached).  But I think this is probably normal behavior.  All the VIs in question are broken due to an unwired input on the bundle.  The bundle is the only thing in these VIs.  Could you please verify that this is the case.  It said the mass compile was complete and I am assuming that it did compile the rest of the VIs, correct?  Unfortunately I am still getting the same message.  Do you have any other ideas?  Anyone?  Thanks again for your assistance.
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home
    Attachments:
    Mass Compile Dialog.JPG ‏338 KB

  • How can I create a Report with the Report Generation Toolkit?

    Hi,
    I have installed Labview Report Gerneration Tool for Microsoft Office Version 1.1 and now I want to use MS Office Report Express VI but it need the VI "Dflt Data Dir.vi". I don't have this on my computer, why? Where can I get this VI? Can somebody help me?
    thanks Labprog

    Hello Labprog
    This VI should be located in the file.llb in the folder
    ..\vi.lib\utility. Thus, it is not part of the report generation
    toolkit but of LabVIEW. I am not sure why you are missing that file on
    your PC, maybe you just did not find it because it is hidden in a LLB.
    Maybe this LLB is not part of your LabVIEW package (Base, FDS, PDS).
    Anyway, I'll attatch that little VI, hoping that this is the only one missing.
    Ingo Schumacher
    Systems Engineer Sound&VibrationNational Instruments Germany
    Attachments:
    Dflt Data Dir.vi ‏11 KB

  • Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

    Hi all,
    I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
    I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
    I have made some steps, like "Open Workbook", "Write Data", etc.
    My steps run well, excepts one step : "Close Workbook".
    If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
    But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
    I feel that I'm trying to use a reference which has been killed in the "Stop" step...
    I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
    Thanks,
    Callahan

    Hi Callahan,
    SignalExpress (SE for short) does the following on the Stop event:
    1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
    2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
    3. The VI is then run, with those values and states.
    4. SE checks to see if any errors where returned.
    5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
    Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
    Hope that helps. Feel free to post your LLB if it doesn't.
    Phil

  • Report Generation Toolkit Error (undefined erro)

    Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.
    I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).
    Any ideas? 
    nrp
    CLA

    nrp wrote:
    I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.
    Was it the first time you attempted to write the table to that spreadsheet?
    Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.
    What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...
    - Partha
    LabVIEW - Wires that catch bugs!

  • Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

    Hi everybody,
    I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit.  My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
    "Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi"  That is the exact wording, even with the weird punctuation and capitalization.
    The first occurrence of the error is not determinate.  Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up.  Once this error occurs, I must quit LabVIEW to resolve it.  If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs.  Excel_Open.vi is another.
    These logging VIs have worked just fine until upgrading to Excel 2007.  I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1.  I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support.  However, even after upgrading, I'm still getting the same errors.  I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application.   The error occurs both in the LabVIEW IDE and in the built application.  Does anybody out there have any idea what I can do to fix this?  I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
    Thanks,
    Phil
    Solved!
    Go to Solution.

    Hi Christian,
    I do not see that exact option listed, do you mean "user interface"?  I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
    I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller".  Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
    Thanks,
    Phil
    Attachments:
    VI_properties.png ‏15 KB

  • Report generation toolkit VI error when running EXE

    A VI inside the Report Generation Toolkit (version 1.1.2), Excel Find Application Directory.vi, will not function correctly when running an EXE.  The "Current VI's path" block will return the path of the currently running EXE rather than the path of the Excel Find Application Directory VI.  (The same would be true for Word Find Application Directory.vi.)
    -Joel
    Solved!
    Go to Solution.

    Have you had a look at this knowledgebase article? The error is caused due to the exclusion of any dynamic VI.
    Ipshita C.
    National Instruments
    Applications Engineer

  • Error involving Report Generation Toolkit and Labview Run Time Engine

    Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

    I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
    Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
    I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
    I displayed my App.Property of APP.DI
    R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
    Any ideas ?
    Greg Klocek

  • Report Generation Toolkit V9.0.0 : Print Report.vi doesnt print

    Hi,
    i have migrated my Labview 8.5 Project with Report Generation Toolkit V1.1.2 to a Labview 2009 System with Report Generation Toolkit V9.0.0.
    In this Project I use the Report Generation Toolkit for printing out a Standard Report with e few Tables and Graphs.
    Now the VI Print Report.vi delivers the Error -41002 with the Text "Invalide Printer Name". I have, of course installed the propper Printer on the machine.
    I don´t connect a string to the "Printer name" input of the VI, because i want to use the default printer.
    In my oppinion, there´s  a bug in the Print Report.vi: if you don´t wire the "Printer name" input, the vi should use the default printer, but in this case the vi connects the empty input string to the input of the method node it calls.
    I fixed this bug, but the method node still returns the same error.
    any ideas?
    Thanks!
    Solved!
    Go to Solution.

    Thank you for the link!
    For some reasons i can´t find this specific article in the knowledge base (my browser is always rerouted to the german version of ni.com, because i am in Austria). I tried to search with the exact title of this article, and the error message string, but no results...
    I have also installed Labview 8.5 and the "old" Toolkits on my new computer in addition to Labview 2009 and the "new" Toolkits and tested my program in 8.5. Here i got an error mentioning the margins and i had to change the margin settings for printing out, then in worked.
    After reading the article, i have applied the same changes for the margins in the 2009-version of my program and it works too!
    Problem solved!
    Thank you very much!
    PS:
    I first wrote, that there´s maybe a bug in the new version of the Print Report.vi, but i´ve compared it with the old version and it seems to be no bug, sorry!
    After all I decided to stay with Labview 8.5 for now, because of another problem:
    it´s not possible to "save for previous version" from LV2009 to LV8.5 directly.
    Laview crashes, when a VI contains an event structure as i found out by searching through the "known issues", and i have a lot of VIs with event structures!
    I have to have the possibility to save my Labview projects for 8.0 and 8.5. The only way is to save for 8.6 and then save from 8.6 to 8.5.
    That´s nasty and time-consuming!
    Maybe a future update will solve this problem (without producing new ones)

  • Report Generation Toolkit Error Quick Question

    Hi,
         I created the most awesome LabVIEW report ever at my desk using a trial version of the RGT and Office 2003.  I took this to my production machine and ")@#(&%(*#^%()^!!!"  The production machine has office 2007 and a fully licensed version of the RGT.  Both machines have LabVIEW 8.6.0.  I've read all the stuff about these errors and something about classes and dll's and whatnot's.  So my quick question, is:  Instead of matching the versions of Microsoft Office as recommended, can I just rewrite from scratch the VI that creates this world's most awesome LabVIEW report on the production machine to create the same effect? 
    Solved!
    Go to Solution.

    Hi 
    Quick Answer: Probably
    Slower answer: Microsoft changed a lot of things behind the scenes in Office 2007, but the Report Generation toolkit version 1.1.3 supports Office 2007 so you should be good to go. Depends on what functions are included in your VI. Liek the read me says "Several default settings in Microsoft Office 2007 differ slightly from previous versions. Reports you generate using Office 2007 might look different than reports you generate from other versions of Office because font sizes, cell sizes, and so on, differ."
    Best Regards
    David
    NISW

Maybe you are looking for