Error -2147417846 in Word_Get_Range.vi in Report Generation Toolkit RGTK

Hi,
in my large app there's a need to report lots of text results to various positions in the report. I've created a template with roughly 200 bookmarks. And I've got a wrapper around 'Append Report Text Str.vi' that stores an array of strings at an array of bookmarks. This one runs quite OK most of the time, especially since I've put a 200ms delay into the for loop that calls 'Append Report Text Str.vi' as often as required. But sometimes I got the error Error -2147417846, which is basically caused by Word_Get_Range.vi. Finally this states, that 'the application is busy' (my translation of a German error message). I assume that this means that MS Word 2k is busy.
IS THERE ANYTHING I CAN DO?
* Assuming that the whole RGTK is based on Active-X calls to MS Word 2k, is there any means to detect such situations when Word is busy?
* How much calls can it accept?
* Is there any delay that keeps those errors from arising?
* Does this error mean that the last text was not written and the call must be repeated?
I've got the impression that the whole RGTK is not that rock solid stable; Sometimes I got weird error messages within Word, for example that the hyphenation module for Italian Language could not be found. But I'Ve never ever used anyting with Italian, neither installed support for this nor do I speak Italian.
Any Ideas?
Greetings from Germany!
Uwe

Waterman,
Watermann wrote:
hi Uwe,
sorry, but I found nothing relating to this error number.
how is the behaviour when increasing the loop delay?
is it possible to test the application with MS Word 2003?
greets!
At this time I have a delay of 250 ms inside the loop and it works most of the time when adding text strings only. It breaks however when I attempt to add a graph into the report and than have the loop with other text strings following quickly. In execution highlighting mode it works reliably.
Ähm, maybe I could try getting a Word2003 license. But I'd prefer avoiding the hazzle of upgrading just for a try.
I was a technical author for several projects and with several version of MS Word. My impression was that there have been just a very few bugs that had been fixed with newer versions. Almost ever they introduced new features with new bugs instead.
So if you have a good reason that this would help, I'd try it.
Thanx for your reply!
Greetings from Germany!
Uwe

Similar Messages

800706BA RPC server unavailable in Report Generation toolkit

Hi all,
I've got a problem with LabVIEW 7.1.1 and Report Generation Toolkit (RGTK).RGTK is used to connect to MS-Word, create a new document from template and report test results. Works like a charme when stying local on the respective test machine.
LabVIEWs 'Automation Open' node as wella as other parts of the RGTK have an control 'machine name' so I suspected I could bring a report server into game. Tried it and get an error "0x800706BA - The RPC server is unavailable in myTestVI" (translated from German Windows error).
All the required subVIs to create a document have been put into a small test app. This one runs fine when running on the desired report server, but fail when opened and run on the devellopment machine.
I have searched extensively for that error code and have changed some port settings in the firewalls and some services settings with no success. Can anyone help me out?
BTW, on the remote machine a new process named WINWORD is started, but nothing more.
TIA!

Hi Lul,
The error 0x800706BA is, as you said, a windows error (and, btw, your translation was correct as the original title is "The RPC server is unavailable").
You can try to fix it with MicrosoftFixit :
http://go.microsoft.com/?linkid=9666880
Beside, more links that could be of some use :
Windows Update error 800706BA:
http://windows.microsoft.com/en-US/windows7/Windows-Update-error-800706BA
Microsoft answer about error 800706BA:
http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_update/microsoft-updates-fail...
In addition, a KB which is also related to this "RPC Server unavailable" in our IT database:
How to fix MSI software update registration corruption issues:
http://support.microsoft.com/kb/971187
Regards
Florian Abry
Application Engineer Group Leader
NI Germany

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 (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 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 and Office 10 - build errors

Using LabView 2011 and Report Generation Toolkit 2011.
After installing Office 10, I would get build error for Excel-Print.Vi and Excel-SetCell.vi and build is then aborted.
2011/vi.lib/addons/_office/_excelsub.llb/Excel-Print.vi.
Says it is unable to save a vi without a block diagram.
Uninstalled Office 10 and reinstalled Office 2003 and build went thru just fine.
I can program using Excel 2003 and the compiled executable will work on another computer with Excel 2011 but once I install Office 10 on my LabVIEW computer I cannot build.
Can't believe I could be the only one to experience this. Any workarounds?

Duplicate Post

Error -2417417851 using Report generation toolkit

I try to use the Report Generation toolkit (Version 1.0.1) for MS Office und the example "Generate Report from Template (Excel).vi" return an Error -2417417851
I run Labview 6.02, on Win2000 German, and use Office 97 (Everything is installed (included MS Graph))
Did someone experienced such a problem and found a solution?
Thank you for your Help!

Is LabVIEW and Office both German? Under Control Panel >> Regional Options >> General, is the language set to German? How about under Regional Options >> Input Locale? Reboot if you make any changes.
I would suggest reregistering the nireports.dll. It is located in the National Instruments\Shared\NI Reports directory.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/4f811a9b23f1d46e862566f700615b7a?OpenDocument
Next, mass compile (Tools >> Advanced >> Mass Compile...) the LLB's in the \vi.lib\addons\_office
Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

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

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 7 with Report Generation Toolkit

Hello Everyone,
I'm trying to generate an Excel sheet report for some readings using "Report Generation toolkit" But when trying to generate the report, the report generation part of code is executed and gives Error(7) and there is no report is generated.
The Code I use is atached in the following Link:
https://www.dropbox.com/s/9n4brimucsd0xts/Report%20Generation.rar
Can I get help please?
Thanks in advance
Solved!
Go to Solution.

I was able to download and open your compressed file. I unpacked it into a folder.
There are numerous peculiarities that lead me to ask "Are you trying to learn LabVIEW on your own, without a mentor and without training and guidance"? Here are some of the things that I noticed:
Although a Report Generation .lvproj, .aliases, and .lvlps file, the Project, when opened, was empty! Since Projects were added to LabVIEW, almost all development should take place in a Project, but you do not appear to be doing so.
You have an Event Loop (good) to handle pressing Start, Stop, and Report buttons. But instead of using Boolean controls with a Latch property and using a "Value Changed" event, you use Switch Until Released (which, so far, I've never used) and a Mouse Down Event. I suppose this could work, but I've never seen this pattern.
You are writing an Excel Report, but are not using the Excel-specific VIs (such as Excel Easy Table). Why (or Why Not)? The basic idea of an Excel Report is that you create the 2D text data you want to write into Excel, then with a few simple VIs, you open Excel, write the Table, and save the Report. In particular, you don't write out something that resembles the columns of the first few rows of a Spreadsheet (Date, Time, Test, etc.).
Now to your specific question, Error 7. Do you know what this error means? If you click on Help, choose Explain Error, and put in 7, you will see this means "File Not Found". Well, there is an obvious place where a File is used, right when your program starts. I recommend that you put a Probe (do you know about Probes?) or an Indicator on the path going into the main For loop and see what File you are trying to open (hint -- there's an error in the way you build the path, but you should be able to figure out how to fix it).
Good luck. Hope these suggestions get you on a Better Path.

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

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.

Error -2147417846 in Word_Get_Range.vi in Report Generation Toolkit RGTK

Similar Messages

Maybe you are looking for