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

Similar Messages

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

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

    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

  • 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

  • Generate report using Word Report Generation VIs error

    When I Generate report using Word Report Generation VIs  ,the error is generated.
    This is  my Vi
    can somebody  tell the error reason?
    The attaché is Vi (one is 2011,other is 8.6)
    Attachments:
    report-8.6.vi ‏16 KB
    report2.vi ‏33 KB
    template.doc ‏40 KB

    Hi Ben64
                 Thank you! The problem is solved.
       BUT when I use the Word Easy Graph vi  ,the result is
    I want the Graph (curve),like as:
    How Can I do get the picture.
    I have other problem. I want to get default name for the new word file.
    liang

  • 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

  • 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

  • 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

  • Is ms office 2013 supported for report generation​? Error 41106

    Hi
    I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
    I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
    When using the report generation toolkit, I get an error 41106.
    I have reinstalled the toolkit - no effect.
    I sort of assume therefore that office 2013 is not supported?
    Any hints, tips, patches or workarounds please.
    Bill

    Bill_Shepherd wrote:
    Hi
    I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
    I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
    When using the report generation toolkit, I get an error 41106.
    I have reinstalled the toolkit - no effect.
    I sort of assume therefore that office 2013 is not supported?
    Any hints, tips, patches or workarounds please.
    Bill
    I've seen some issues when I upgraded to Office 2010. Note that it is possible that the route cause of your problem is totally different but in my case there was some ActiveX properties or Methods call that have been changed. I solved this issue by navigating to the property/method that caused the error, clicked on it and reselected the same property/method. You could probably find some older post that discuss that. Hope this help.
    Ben64

  • 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

Maybe you are looking for

  • Anyway to capture HD on my 2.5 dual?

    Question says it. I've been looking all over, and the only thing I found so far that actually works is the DeckLink from BlackMagic -- $995! Anyone have a better suggestion...?

  • PSE 7: Texture folder has JPG and PSD files?

    I noticed there are both file types in C:\Program Files\Adobe\Photoshop Elements 7\Presets\Textures\ Blue Pastels.jpg Burnt Red Pastel Paper.jpg Charcoal on Paper.jpg Dirt.jpg Feathers.psd Footprints.psd Frosted Glass.psd Granite.jpg Grass.jpg Lambsw

  • If I use blast option in zone prefix command

    Hi, I would like to introduce in our network the remote zone gatekeeper redundancy. I saw there' s a "blast" option in zone prefix command. Could I use that without problems? Thanks. Regards, Paolo

  • Sound blaster live 5.1 digital drive

    I bought this from newegg model no. SB0220 sn. MSB02243440746S and can not find drivers?

  • Track stack and mixer view

    Ok! You can't move mixer channel. Why Apple I don't know!? Then you create Track Stack. Awesome! This way I can have several tracks needly....stacked. But why in the name of GOD are the the mixer channels all over the place? Or should I RTFM?