LabVIEW 8.6 and report generation toolkit

I was wanting to upgrade to 8.6 but noticed that my rep gen toolkit(1.1.1) is not compatible.
Will NI be offering a free upgrade? or do I have to go to management and ask to purchase rep gen toolkit 1.1.3 for 500 US dollars? Purchasing the same toolkit every few years when you have an SSP for a full development system is getting kind of old.
Brian

Unfortunately there is some delay in us Aussies getting the original DVDs sent to us, so at this stage my NI rep has burned me a copy of the main LabVIEW install but I can't find the Report Toolkit on it.
I am an SSP customer but when I go to the Services Resource Centre I get this message:
Important Message
Access to the Services Resource Center could not be verified.
The email address is not subscribed and/or activated with the appropriate level of service. If this is the incorrect email address, please login here
Please confirm that your correct country information is specified, please select here
If you have just subscribed you may need to wait up to 48 hours for your subscription to be processed
If access is urgent, or to subscribe, please contact a NI Representative at (800) 206-2179. Outside of the US and Canada please contact your local NI branch office

Similar Messages

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

File Dialog and Report Generation Toolkit

Hi,
I designed a VI for an electrometer calibration and it works quite well The only problem I have is the following:
I used the Report Generation Toolkit to put the measurement data in an Excel file. When I run the VI I'd like a window to pop up to define the location and name of the Excel report file. If these two things are done LabVIEW should create the specified Excel file and run the rest of the code.
So i tried this with the "File Dialog" Vi and all the needed low-level File I/O VIs and it worked.
But when i connect the "File Dialog" VI with the "New Report" VI of the Report Generation Toolkit I get an error message.
Is there any solution to get this file dialog pop up window with the Report Generation VIs?
thx for any help...!
Message Edited by Flea on 12-15-2005 03:58 AM

Wow, thanks for your fast and very helpful reply devchander!
I already tried this and it works fine
thx!

LabVIEW 8.5.1 / Report Generation Toolkit / Office 2k3 & 2k7

Hi
I have just upgraded from LV8.5 to LV8.5.1 and it's toolkits and I don't see the report generation toolkit in my menu.
I would have accommodate myself if the problem was only with menus, but now some of the vis included in the toolkit don't work anymore.
I verified in C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\_office and everything seem to be installed...
I was wondering if it makes a difference because I have both Office 2k3 and Office 2k7 installed on my machine.
Everything was working well with LV8.5 and both installation of Office.
I have tried to reinstall/repair the report generation toolkit, but nothing change.
Am I the only one with this problem?

It is true for each updater, that it overwrites the NIReport.llb. I just copy the llb into another folder and after updating but before mass compile I copy it back again. This worked for each update (7.1 -> 7.1.1; 8.0 -> 8.0.1; 8.2 -> 8.2.1).
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Build usuccessful in LV8.0.1 and Report generation toolkit 1.1.1

I am trying to build an executable. I had included _wordsub.llb and _exclsub.llb as dynamic VIs.
This message is all what I get and no executable is created.
The file already exists in the destination.
C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\addons\_office\_wordsub.llb
Any ideas?
Scientia est potentia!

This appears to be a duplicate post. Check out my response to the other thread here.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

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/C38CE3F30542D65B86256F0E00740DD8
Prashant.

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

Hide Excel Chart Legend Using LabVIEW Report Generation Toolkit or Active

Hello Eveyone:
I work on the report generation toolkit in labview and creat the report in excle. I create the chart into report but I can't hide the chart legend or change the font size using report generation toolkit.
I appriciate you guys time.
Thanks
Solved!
Go to Solution.

Howdy!
What is the version of LabVIEW and Report Generation Toolkit you are using? Have you taken a look at the LabVIEW Example Column Graph (Excel).vi
and looked at the help for Excel Insert Graph VI and Excel Set Graph Font?
Joshua B.
National Instruments
NI Services
NI Support Resources
NI Training Resources

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)

Problem with report generation toolkit when installed new office 2010

Dear all, I had LabView 8.6.1 and report generation toolkit for MSoffice 2003 perfectly working in my laptop.
Now I have added MSoffice 2010 and report generation toolkit does not work anymore since it is linked to new office.
How can I inform Labview to link report generation toolkit to the old MSoffice 2003?
regards
Max

The Report Generation Toolkit is ActiveX based. When you install the newest version of Office it registers the ActiveX server for that software, which the toolkit adapts to and uses.
Uninstalling Office 2010 would solve the issue, otherwise you will need to look at unregistering the 2010 component of Office ActiveX - but I'm not sure if that's possible.
Regards,
Peter D

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

Application builder-Office report generation toolkit

Hi,
I remember there was a trick to get the executable work with different
versions of Microsoft office but I cannot find it now. The problem it to get
the exe work with some other office version that it was made. I use LabVIEW
7.0 - 7.1 and Report generation toolkit 1.01 for Microsoft office. Was that
possible?
Thanks Eki

Eki,
When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work.
Zvezdana S.

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

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

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.

LabVIEW 8.6 and report generation toolkit

Similar Messages

Maybe you are looking for