Report Generation Toolkit failure with Win 7 and Labview 2013

I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files.  If I try to run the New Report.vi with report type Excel selected I get  error -2146777998.  Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error.  Selecting Standard Report or HTML also run without errors.
I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
Solved!
Go to Solution.

I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report  by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt.  The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

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 Compatibility with Microsoft Office 2013 and LabVIEW 2012

    Hello community,
    on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
    In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
    Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

    Hi digital_badger,
    as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
    1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
    2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
    Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
    3. You could leave your setup as it is and stick to your MS Office 2010.
    I hope I could give you a good answer to your question

  • Report generation toolkit problem with office 2000 and office XP

    Hello, I am having a problem with running my vi after it is compiled with application builder. The dev machine is an XP box and the targer is windows 2000. I included _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi from the office 2000 section of the install cd (for the report toolkit) in the compile but did not include those files for XP. When I run the application on the target machine (2000), the reporting functions call Excel just fine and the program does not come up with any errors. The program however, is not loading the approprate template and inserting the approprate data. Did I leave some neccessary files out of the compile? Thanks in advance!
    Greg
    Gregory Osenbach, CLA
    Fluke

    Hi Acer,
    The recommended procedure in your case is to install Microsoft Office 2000 on the development machine and then reinstall the LabVIEW Report Generation Toolkit. When the toolkit is installed, it will check for the current version of Office and install the corresponding VIs to support it. The VIs include different ActiveX calls according to the version of Office. Therefore it is not enough to change the support manually without having the correct version of Office installed first.
    However, I would recommend that you just try to run your executable on a machine that has Office 2000 installed. The difference in the ActiveX API for Office XP and 2000 is not that significant, so your application might work perfectly on an Office 2000 machine. If you try to run the executable on a machine with Office 97 installed I'm willing to bet my right arm that you will experience errors.
    Good luck Acer!
    - Philip Courtois, Thinkbot Solutions

  • Report generation toolkit (1.1.2) and 8.5

    I am not as crazy as I thought!
    I wrote a program today that collects data from excel reports in many directories using cell names and it worked well.  Unitl I saved it.  I had been saving the sub vi's, but when I went to close them I got a message about unsaved changes and I guess I clicked to save the changes today.  The program never worked the same again.  I would get errors like 41106 and 41110 at random (problems with excel not opening and other stuff).  I tried adding waits which slowed everything down and worked mostly.  But the only way to not drop data and get errors was to have a copy of excel open while getting my data.
      Well I just uninstalled/reinstalled the toolkit and rebuilt the vi that was having problems with the fresh install and everything is great again.  So my question is why does the toolkit have problems when I save it in 8.5?  The warning does say that the vi's are from 7.1 and I cant find any updates so I am hoping this is the latest version that came with my 8.5 suite.

    Hi Bryan,
    There should not be a problem with saving the VIs from the Report Generation toolkit in LabVIEW 8.5. I have checked the readme files to make sure but RGT 1.1.2 should work with any version of LabVIEW later than 7.0. However, the readme does discuss an specific upgrade issue. It says if you previously created VIs that use the built-in Report Generation VIs in LabVIEW Professional, Full, or Base packages or VIs from a previous version of the Report Generation Toolkit, installing the Report Generation Toolkit 1.1.2 might break the VIs you created. If the VIs you created contain any of the following VIs, edit them so they are compatible with the Report Generation Toolkit 1.1.2.
    Append Front Panel Image to Report VI—The Image Format input of the LabVIEW 6.1 version of this VI is a different enumerated type than the current toolkit version. Right-click the input and select Create»Control or Create»Constant from the shortcut menu to create a compatible control or constant.
    Append Table to Report VI—The connector pane position of the show grid lines input changed from the Report Generation Toolkit 1.0.1 version of the VI. Reconnect the original wire to the new input location.
    Get Report Settings VI—The cluster order of the font settings input changed from the Report Generation Toolkit 1.0.1 version of the VI. Right-click the output and select Create»Indicator from the shortcut menu to create a compatible indicator.
    Report Express VI—If a VI includes the LabVIEW built-in version of the Report Express VI on the block diagram, the VI breaks after you install the Report Generation Toolkit 1.1.2. Double-click the Report Express VI to launch its configuration dialog box, then click the OK button. Reconnect all wires to the Report Express VI.
    You might need to relink the following subVIs after installation because the connector panes changed in the Report Generation Toolkit 1.1.2. Right-click the VIs and select Relink to SubVI.
    New Report
    Dispose Report
    Append Front Panel Image to Report
    Append Hypertext Link Anchor to Report
    Append File to Report
    Append Horizontal Line to Report
    Set Report Font
    One thing that might have happened is if you had created the program in an earlier version of the toolkit, then saved it in the new version of the toolkit, maybe some of the upgrade issues regarding the VIs listed aboved cause LabVIEW to start giving you errors. Also, which version of excel are you using? After you re-did the VI program, have you tried to save it again and see if the same problem occurs?
    Carla
    National Instruments
    Applications Engineer

  • Office Report Generation Toolkit 1.0.1 and MS Office 2000 problem

    Hello.
    I'm tring to make a repot in word using a template..everything works just fine when in development..but when i make the executable the problem arises.
    I get error code 7  (Cannot open vi reference) in NewReport.vi.. FYI i'm running the aplication in the same machine i'm developing.
    I'm sure everything else is ok..- changed paths to work in executable, template in correct folder...i'm adding the necesary support llb to the executable(Win200), etc - ..i tried reinstaling office and the report generation toolkit but i still have the same problem...
    How can i solve this?....
    Thanks in advance for all yur help.

    Well..that was a very good answer to my question...and it solved my problem. Thank you.
    I thought that by adding just the llb as support files would be enogh..but now i see this is not correct..thanks again.

  • 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

  • Report Generation Toolkit on Vista and Office 2007

    Hi,
    I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
    The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
    The installation stops and the toolkit is not installed.
    What can I do ?
    Tom

    Tom SAVU wrote:
    Hi,
    I am trying to install Report Generation Toolkit 1.1.2 on LabVIEW 8.5 on a computer with Vista Business and Microsoft Office 2007.
    The installation is starting, but I am receiving a message saying that "Microsoft Office 2000 or later is not detected on the computer"
    The installation stops and the toolkit is not installed.
    What can I do ?
    Tom
    The Report Generation Toolkit does probably not support Office 2007 yet. This is because the Office ActiveX interface used to change with each version and the Report Generation Toolkit comes with specific libraries for each of the Office versions it supports. With the wrong office version the Report Generation Toolkit VIs are normally broken and can't run without some more or less involved modifications.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

    I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
    Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
    Any ideas?
    Scientia est potentia!

    Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files?  I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs.  I think I've seen a similar post on the discussion forums in the past that recommended this.
    If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
    Good luck,
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • What is wrong with the report generation toolkit????

    OK.  Now I'm a little frustrated.
    I started this thread, but then made an ugly workaround until someone tells me the correct solution.
    So now.... my compiled application can find all the toolkit VIs... but I get error messages telling me that the VIs were are too old (V 7.0) to be recompiled to Version 8.5.1.
    When I got the first of these messages, I opened and saved the VI indicated.  That just pushed the problem along to the next VI.  So I said "ah ha!" and went to the directory (blah\blah\....\addons\_office) that has the toolkit routines and did a Mass Compile.  No errors were generated by this.
    NOW when I try to run, I get an error message telling me that Excel_Insert_Text.vi is not executable.  But that is clearly a lie.  When I open the VI in the development environment, there are no broken arrows...
    And let us not forget my application runs perfectly and without errors in the development environment, even after I brutally recompiled everything.
    For those who care:  I'm running V 8.5.1 with whatever version of the Report Generation Toolkit comes with that (1.1.2??).
    Arrgh.
    -GN

    I feel your pain GN... the RGT in its current Classes incarnation has a few "issues"... try deploying it with TestStand a whole world of pain opens up.
    Now, I have recently seen an issue very similar to the one you described, I broke the RGT after doing a mass compile.
    Eventually opened the RGT VI that was "broken", it looked fine to me. It was something to do with setting the font, and was basically just an activex call. Eventually out of frustration I right clicked on the node, reselected the same method, and another input parameter line appeared at the bottom of the node and the VI all of a sudden became runnable. WOW!
    This needed to be done in a few of the VIs.
    Maybe this will help you
    nrp
    CLA

  • Control checkbox form field in word with report generation toolkit for Microsoft office

    Hi all,
    Happy New Year!
    I insert in the word template the check box form field. It has a bookmark name "Check1".
    Now I'm trying to checked or unchecked this field using the report generation toolkit for Microsoft office and I couldn't. If anyone now how to do it? I'm using LabView 8.0
    Thanks in advance,
    Boris
    Solved!
    Go to Solution.

    Boris,
    The Microsoft Office Toolkit does not have support for checking/unchecking check box forum field. You would have to research the activex functionality that enables this to be checked or unchecked and then do the activex calls yourself. I did hear of one csutomer who used a special font to write a blank box or a checkbox into a word document and changed it that way as well.
    Maybe http://www.ozgrid.com/forum/showthread.php?t=53715 gives a hint to an activex reference
    Rob K
    Measurements Mechanical Engineer (C-Series, USB X-Series)
    National Instruments
    CompactRIO Developers Guide
    CompactRIO Out of the Box Video

  • Report Generation Toolkit using Chinese Characters

    I am trying to use the Report Generation Toolkit for Microsoft Office under LabVIEW 8.0.  I would like to use Chinese characters for the headings of the columns using a 2D array of the headings and the Excel Easy Table.  When I generate the report, the text of the headings appears to be jumbled and not encoding correctly.
    For example:
    仪器编号 becomes êNhV÷S
    采前初重（g） becomes Ç‘MRRÍ‘ÿg
    Any insights here? Thanks

    Hi,
    what you describe reminded me of a bug fix in the Report Generation Toolkit 2012 :
    339092
    Using the "Append Table to Report" VI to add strings of Cyrillic font to a table in an MS Word report results in gibberish being added to the report.
    http://digital.ni.com/public.nsf/allkb/09D6DE5170B3C0BD86257A2B004CFD20
    I know that Cyrillic and Chinese characters are different but they are often confronted to the same problems...
    Aurelie

  • I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 profession​al. The create new report VI opens Excel but throws error (-21471672​62- from automation open VI) when I try to open MS word. please help...

    I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

    Hi Leo22,
    Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
    Jeremy L.
    National Instruments
    Jeremy L.
    National Instruments

  • 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

  • Can't print to Epson TM-U590 Slip Printer from Report Generation Toolkit with LabVIEW 8.6.1

    Hi all,
    I have an application that uses the Report Generation Toolkit to print tickets to a docket printer.  Usually this works fine - I have 8 existing installations where there are no problems
    I'm currently installing the software at a new site that uses an Epson TM-U590 slip printer and I can't for the life of me get printing to work
    Using a Standard Report, the Print Report.vi returns error -41002 which indicates it can't find the printer.  I've opened up the VI using remote debugging and it does find the printer name correctly with the Query Available Printers.vi.  It gets an error code -2147352567 from the Printout node, which then gets replaced with the -41002 error which is reported.
    For historical reasons I'm still using LabVIEW 8.6.1 for this project.  I'm considering moving to 2011 or 2012 but I've had reliability issues with other parts of the application after attempting to update to a newer LabVIEW version so I'd like to avoid that at this stage.
    The application is running on a standard desktop PC with Windows 7.  The slip printer works fine if I print to it from Notepad, and my application is happy to print to any other printer, just not the slip printer.
    The slip printer is using the LPT port.  Previously the docket printers I've used have been USB but I would expect the printer driver to hide this detail from the application...
    Any ideas would be much appreciated
    Cheers
    Brett
    Senior Software Development Engineer
    Certified LabVIEW Architect and LabVIEW Champion
    Solved!
    Go to Solution.

    I've managed to sort out the problem, thanks to this KB article: http://digital.ni.com/public.nsf/allkb/67D60209102E2161862568AC0074BF64
    I'm now having the same issue with a Star docket printer (a TUP592), this time with another program developed in LabVIEW 2011.
    As mentioned in the article, the problem is actually to do with the margin settings rather than the printer name, despite what the error message says
    After some experimentation, I've gotten the Star printer to work by setting a large (>14cm) right margin.  No idea why this is required as it seems to print right up to the right edge of the paper quite happily, but there you go.
    So I haven't defintely fixed the original problem yet as I haven't gotten back to the site, but hopefully this will be of some help to someone else.
    Cheers
    Brett
    Senior Software Development Engineer
    Certified LabVIEW Architect and LabVIEW Champion

Maybe you are looking for