Microsoft Report Generation Toolkit Error Running VI's

I am using LabVIEW 6.1 and Microsoft Office 97. I have installed and reinstalled the Toolkit. Whenever I try to run ANY sample VI's that come with the toolkit (by going to "FIND EXAMPLES"), none of them run. The ERROR LIST says that none of the subVI's are found. Why are these subVI's not being found? I see that they are there. Is there a directory error? Both LabVIEW and the Toolkit were installed in their default directories. The Toolkit is in C:\Program Files\National Instruments\LabVIEW 6.1\vi.lib\addons\_office
Advice Please?!
I'm attaching a screenshot.
Attachments:
screenshot.jpg ‏72 KB

I would also suggest to mass compile the office VIs.
Looking at the image I notied there are coercion dots which indicate the report references not quite match.
Joe

Similar Messages

  • Word report generation toolkit error with Win 7 LabVIEW 2013, Word2010

    Hi All
    I'm seeing different Errors using the Report generation toolkit. Maybe you can help me with that.
    The errors are:
    -2147417846, application is busy in Word_Get_range.vi
    -2146824090 Exception in Microsoft word: Befehl misslungenHelp Path is wdmain11.chm and context ...
    -2147417846 application is busy in Word_Quit.
    the error messages are attached to the post.
    I'm testing 10 sensors with one application and want to run up to 5 applications on one computer. Since I'm seeing such errors as application is to busy I set all my report generation vi's as non-reentrant execution and additionally added some pause after each word modification.
    But I'm still seeing such errors when I run two applications on one computer.
    What is the best way to deal with these errors?
    thanks
    best regards
    Urs
    Attachments:
    exceptionerror.PNG ‏20 KB
    BusyActiveX2.PNG ‏20 KB
    BusyActiveX.PNG ‏22 KB

    Here my Vi's involved in creating the report.
    Is there a way to check wheter word is busy or already open?
    Attachments:
    save report as PDF.vi ‏26 KB
    create_report.vi ‏70 KB
    Word_Update_Table.vi ‏34 KB

  • Report Generation Toolkit, Error 1706

    I'm trying to run some report generation toolkit examples, typically those that plot data in various charts in Excel.
    However I'm consistently receiving the attached error, seemingly saying that I require Microsoft Project -- something that seems strange.
    Attachments:
    NI Example Finder_2012-02-22_14-42-56.jpg ‏55 KB

    Sunshine's recommendation is a good one. In terms of the problem itself I suspect that the problem isn't in the LV world at all. I have had problems multiple times were attempting to open a file caused Windows to try and install a completely different program. The last time it happened, I never did anything to fix it, it just stopped doing it one day. The other times I ran some basic system cleanup (using ccleaner), removed stuff that I knew I didn't need and the problems cleared.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • 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

  • Report Generation Toolkit - Error message rpcrt4.dll

    Hello
    My labview app. calls functions from the Report Generation Toolkit. I tested the runtime version, and this work fine under in Windows NT and Windows 2000, but does not work under Windows 98. I got and error message say "rpcrt4.dll Page not valid" that seem come from Windows and is related to a Remote Procedure Call. I already check the version of this dll 4.71.2900

    The rpcrt4.dll is part of the DCom98 package. I have seen other problems, unrelated to LabVIEW, with this .dll arise when other programs have installed different versions of some of the DCom DLLs. You may want to consider trying this program out on another Win98 machine, or you may want to search through the Microsoft Support page for errors with this dll, specifically with the error number in the message you receive. The ones that I have seen have suggested restoring the DCom dlls to the original ones from the Win98 disk. There is also an update to the DCom components for Windows 98 (version 1.3) on the Microsoft website.

  • 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 Error

    I  have an application that generates multiple excel spreadsheets each containing a table and four graphs.  This has been working fine for three months but I am now getting error when generating the reports.  The source of the error is in the Excel_create_workbook as indicated on the attached picture.  I am passing in a template name for my excel reports.  The error code (-2147352571) states a type mismatch.  The file path to my template is a constant so I can't see how sometimes I get a type mismatch and other times I don't.
    Any help on this would be greatly appreciated.
    Thank you,
    AJL
    Attachments:
    create_Workbook error.JPG ‏269 KB

    Thanks for the reply, however, this VI is part of the Report Generation Toolkit so I don't want to have to modified NI's code if possible.  I did try your suggestion without saving the VI and I still got the same error. 
    Any other ideas? 
    BTW - I encountered this problem first in an executable but have since seen the error in the development code.
    Does anyone know if there is a limit to how many times you can create an excel document from LabVIEW?  I wouldn't think so but the error seems to happen if I try to create several (more then five usually) documents at a time. 
    Thanks in advance
    AJL

  • Built labview report generation toolkit cannot run

    Hello everybody,
    I would like to ask some questions on report generation toolkit:
    The program works well in developing mode.
    Then I can build the program into *.exe file.
    However, all functions related to report generation toolkit are not working after I built them into *.exe file.
    (i.e. The program can control equipments and calculate, but cannot open an excel report and write something in it.)
    There are no errors when building the program.
    Is there something wrong with the toolkits or is there some advance settings?
    Thank you very much for your help.
    Best Regards,
    Donald

    Including Report Generation VIs in Stand-Alone Applications (Report Generation Toolkit)

  • Report Generation Toolkit error when running exe not vi

    Unknown System Error in Get Report Settings.vi->Get Current Font.vi->Excel Easy Table (str).vi->insert table and save file.vi->80x test suite.vi
    1. The above is an error I get from my exe
    2. I do not get this error when just running the vi.
    3. On several report gen functions cohersion dots are on my refnum input.  Is this the cause of my problem with the exe? 
    I guess there is an another learning curve when dealing with the app builder. 
    Any suggestions would be appreciated.
    Thanks
    Brian
    CLAD
    Brian

    forget what i wrote. it was my vi. 
    funny, most of the time it aint LabVIEW causing the problem but the program itself.
    Brian

  • Report Generation Toolkit files in incorrect location after installing deployment

    TestStand 2010 SP1 + LabVIEW 2011 + Report Generation Tookit
    After installing a deployment, the location of NI_Excel.lvclass is expected to be at ...\VIs for <project name>\SupportVIs\Excel\NI_Excel.lvclass (see attachment)
    but the path of the file is located at ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
    In the deployment image, under the target folder, the file is in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
    and the lvproj finds the file.
    The lvproj in the installation finds the file in ...\VIs for <project name>\SupportVIs\data\NI_Excel.lvclass
    Renaming the folder from data to Excel fixes this problem.
    Has anyone else run into this problem?
    Attachments:
    Report Generation Toolkit Error.png ‏15 KB

    I am facing the same issue when I create the TS deployment through utility using TS2012.I thought of adding the file to the Teststand workspace and give the destination in to supportVIs directory.But even tthat didn't worked as it was copying all excel vis in to two locations.
    Even adding the Directory path in to TS search directory options  to "\data folder"  is not resolving the issue and LAbVIEW Vis are not able to locate it.

  • 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 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

  • Running macro on Table using Report Generation Toolkit and Office 2003 Incompatible!!!!!!!

    Hi,
    I am using some functions under the Report Generation toolkit (LabView 7.1). We recently updated our test PCs from Office 2000 to 2003. The "WORD IMPORT MODULE.VI" returns error code -41113 when used with Word 2003. No problem on Word 2000.
    In fact even the example VI available under Find Examples - Run Macro on Word Table fails and returns error code -41113 when "WORD IMPORT MODULE.VI" is called on Word 2003. Word 2000 is OK.
    Any one faced this problem???? Any solution to this problem??
    I would greatly appreciate your feedback / suggestions.
    Thanks,
    Mim

    darren,
    thanks for your reply.
    After checking the the property "Trust access to Visual Basic Project" , I get the following error message:
    Exception occured in Microsoft Word, Unable to run the specified macro. Help Path is C:\Program Files\Microsoft Office\OFFICE11\1033\wdmain11.chm and context 37401 in Word Run Macro.vi->SetFirstRowAsTableHeaderforWord(Macro).vi->Generate Report.vi
    I can run the macro directly from Word.. no problem running macros in Excel dirently either. I get error message only when running macro from LabView. So, I doubt if it is an IT issue.
    You don't have a problem with Word 2003 and Word Import Module.vi???
    I am attaching my Vi-Report Generation.vi and the subvi. I would so much appreciate if you run ReportGenerate.vi on your PC and let me know if there is a problem.
    Many Thanks for your help.
    Mim
    Attachments:
    ReportGeneration.zip ‏75 KB

  • Error when using Report Generation Toolkit

    Hi, all,
    I am using Report generation toolkit to generate a report in either
    word or excel format. But i even can't run the "new report.vi". It
    returns an error code of "Bad variable type (-2147352568)", and seems
    this error comes out from the "call by reference" after the
    word/excel's "open VI reference". I have checked the folder
    "C:\Program Files\National Instruments\LabVIEW
    6.1\vi.lib\addons\_office", there are "_exclsub.llb" and
    "_wordsub.llb". The respect VIs are all inside. I don't know why there
    is such error. Currently i am using labview 6.1, Microsoft office 2000
    and Windows NT 4.0.
    Your kindly help will be appreciated very much!!!
    Thannk you in advance!! ^_^
    Your sincerely,
    celery

    So, if you place just New Report.vi on the Block Diagram, wire in the report type and run it, it gives you this error? Do the example programs which ship with the toolset give this same error also? If so, I would just reinstall the toolset first and see if that helps. It sounds like the entire install is corrupt.
    J.R. Allen

  • LV Report Generation Toolkit for Microsoft Office says "This VI or item belongs to a library that is expired or invalidly licensed"

    I have downloaded the LV Report Generation Toolkit for Microsoft Office for evaluation with LabVIEW 2010. The examples for the Help get many errors, including "The subVI is not executable. You must fix all errors in the subVI before this VI can run." and "This VI or item belongs to a library that is expired or invalidly licensed".
    I selected that I wanted to evaluate the toolkit instead of putting an activation code during installation. Installation went OK.
    How can I get the examples in this LV Toolkit to Run so that I can evaluate it?
    Solved!
    Go to Solution.

    Also when I place the MS Office Report function in my block diagram, I get: "Unable to View Properties" popup message and no Contextual Help on the function.
    How can I get these RGT function to work properly so that I can evaluate the toolkit?

Maybe you are looking for