Report Generation Toolkit Installation

Hello!
I need to install the Report Generation Toolkit, but only using Excel 2007.
Is this possible? Or will we need to install a full Office suite? Is there a way to workaround full install?
We'll only be using Excel anyway...
Thanks!

Hey Oley,
I have been doing a bit of research and what I found is that there was a corruption in the Windows Installer database. You can use the "Windows Installer Clean Up Utility" downloaded from Microsoft to remove ALL traces of Office, and then reinstall. This should solve the problem. I found this in another discussion forum with someone else with a very similar issue. I hope this helps!
Carla
National Instruments
Applications Engineer

Similar Messages

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 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 missing VI

LabVIEW version 8.6.1
Report Generation Toolkit 1.13
I have just started work on an ongoing project that others have been contributing to for some time. (Hence the project being in older versions of LabVIEW)
On my PC, I am apparently missing the VI "Word Get ActiveX References.vi"
I do have the version 1.13 of the toolkit installed, just as every other machine that runs this code does. But my word.llb does not contain that VI
I have tried simply copying that VI into the .llb The VI is then found by the application. But is not executable due to this error: This VI is connected with a library that does not include the VI. The VI might have been deleted from the library. Add the VI to the library again or select File»Disconnect from Library.
I have also tried replacing my entire C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\ directory with files from a PC that was working. Again, I get the same error as above.
I did attempt to do a repair on my installation of the toolkit. But as far as I can tell, this didn't do anything.
I also tried simply reinstalling the toolkit. But since it was already installed, it did nothing. I am hesitant to uninstall and reinstall the toolkit for fear of breaking all of my 8.6 projects, as well as possibly my 2009 projects. I wouldn't think it mess with my 2009 installation. But I do know that the order in which things are installed can be critical in system with multiple versions. I'm not sure if this applies to toolkits or not.
This PC also has an installation of LV 2009 SP1, and that version also has the Report Generation Toolkit installed. (although it is a different revision of the toolkit than 1.13)
I know that in the past, multiple versions of this toolkit were not compatible, meaning only one installed version of LabVIEW could have a working Report Generation Toolkit installed. But I was of the understanding that this was no longer a problem. Although it may not be a coincidence that neither of the other development boxes running this code do not have LV 2009 installed.
Has anyone else ever run into a similar problem and found a solution?
Thanks.
Patrick Allen
Solved!
Go to Solution.

Darren wrote:
Back before we unified the LabVIEW and toolkit version numbers (in 2009), there were cases where we didn't change the version number in the registry for one reason or another on a minor upgrade.
Ah. This makes sense then.
I just reinstalled said toolkit from said SSP DVD and although it did tell me that I was about to install 1.1.4, MAX still thinks it's 1.1.3
...except that now I do have the missing VI. This is a good thingTM
I still wonder how it ended up missing, because I'm really sure this is where I installed the toolkit from in the first place. I'll probably never know for sure. But that's a lot easier to take when the code is working.
Thanks!
Message Edited by pallen on 04-15-2010 04:52 PM
Patrick Allen

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

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.

Report generation toolkit 1.1.2 doesn't show up on the panel

I installed Report Generation Toolkit 1.1.2 together with the Labview 8.5. But when I looked into the function panel, it didn't show up. No Labview has been ever installed on this machine. However when I went to control panel "Programs and Features"-> National Instrument, it did show the "Report Generation Toolkit for Microsoft Office 1.1.2" there. So I guess it did install it, but how can I add them into the function panel. Btw, my system is Vista.

Hi lshi,
Glad to hear that reinstalling the Report Generation Toolkit resolved
the problem. To answer your question, the installer prompts for an
installation directory to allow users with multiple versions of LabVIEW
to select a version other than the latest.
Peter K.
National Instruments

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

LV 2011 Report Generation Toolkit Constantly asks for 8.6.1 CD

I am having a strange issue.
Its a bit intermittant, so I will try my best to explain when it occurs.
-If I make a new project and run something from the report generation toolkit, I will get an installer from labview 8.6.1. I am running Labview 2011 and have never had 8.6.1 installed on this computer. It will spend about 3 minutes installing something, then demand a labview 8.6.1 CD.
-If I hit cancel it goes away for the project, until I restart the computer. It does not actually need the CD, it just asks for it. The VI containing the report subvi will execute fine, but if I open any of the front panels I get the installer message again.
-If I have run something that uses the report generation toolkit previously in this login session I do not encounter the bug.
-Restarting labview does not make it appear, only restarting the computer
Solved!
Go to Solution.

There are classes in the RGT that are loaded dynamically. You need to include the VIs in your build.
We found you should add the following two folders to your project and then force them to be in your EXE build.
<LabVIEW>\vi.lib\Utility\LVClass
<LabVIEW>\vi.lib\Utility\NIReport.llb
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

LabVIEW Report Generation Toolkit for Microsoft Office

Hi!
One question. I have bought the LabVIEW Report Generation Toolkit for Microsoft Office
Version 1.0a and am trying to install it under Labview 7.1 but the installation stops with the error: "you need a Labview Version 6.0 runtime engine." Is there any possibility to install the toolkit anyway?
Regards
Stefan

Hi
You can try to update your Version 1.0 to Version 1.0.1. Then it should be working.
Here ist the link for the free update:
http://digital.ni.com/softlib.nsf/websearch/19003CF70BB8A57186256E5A00672E2A?opendocument
if it not works you can try to install the runtime engine 6.0 on your system. her is the link:
http://digital.ni.com/softlib.nsf/websearch/D5F11A64A905DB27862569EC005E31E2?opendocument&node=132070_US
Regards
Manuel

Report Generation Toolkit Excel errors and Libraries, Classes

Hello All,
I'm using the Report Generation toolkit Excel functions to handle some data and create graphs. I'm running into problems with the Add Worksheet.vi. At the very start of the vi, it closes the reference to Shapes. Occasionally, the Close Ref will throw an error. I haven't pinned down the exact cause yet (probably an invalid reference). The error itself wouldn't be a problem. Under other circumstances I would choose to ignore it and continue on. The problem is, this is stored in a Class Library controlled by NI.
Solutions I've tried without success:
1.) Make changes, and save the new vi with another name - can't do it because it's encapsulated and the Library is password protected.
2.) Install toolkit in something other than the default folder, so I can make changes and put it under Source Control - installer doesn't allow a new path to be entered.
3.) Change the vi where it is. This works until I move the source to another computer or I update Labview. At that point I lose all my changes.
Maybe it's just my inexperience with Classes, but I just don't see an elegant solution to this. Ultimately I'd like to copy the library off to somewhere else and put it under Source Control so I can make changes and additions to it (NI folks - providing a password to unlock the lib would be helpful...). Does anyone have suggestions on how I can accomplish this?
Thanks in Advance,
Doug

Hi Ben,
Sorry about the first post. After re-reading it, it sounds more like a frustrated rant than a request for help.
I've attached a simplified vi to try to illustrate the problem I'm having. I'm running Excel 2007. Please open the vi, then open Excel Add Worksheet.vi. At the start of the vi, Close Ref for Excel.Shapes occasionally throws an error. So far, I have not been able to consistently reproduce the error, so I can't really troubleshoot it. As I recall, the error code is 1045. The error is carried through the rest of the vi, causing invalid references to be written to Excel._Worksheet and Excel.Shapes, going out to NI_report.ctl.
So, here are the issues I'm running into (other than the error itself):
1.)Short of closing and reopening the file, there is no way to recover from the error. After the error, there is an invalid reference in Excel._Worksheet. There is no vi available to regenerate references in NI_report.ctl. I could easily write a vi to start from Excel._Application and re-read them, but because NI_report.ctl is in a Class library (controlled and passworded by NI), I can't add the vi to the library.
2.) I found that I could ignore the error by wiring around it. If I disconnect Error Out from Excel.Shapes Close Ref and wire Error In from Excel.Sheets.Count to the Error In of the Close Ref, everything works fine. Under other circumstances, I'd save this with a new vi name (because functionality changed) and continue on. But, because the vi is part of a Class library (controlled and passworded by NI), I can't do this. I can save the vi with the modifications (because Excel Add Worksheet.vi is not passworded), but if I pass the source off to someone else, they will have to make the same changes on their installation of the NI Report Generation Toolkit.
Again, I can't reproduce the error with any regularity. I've run the example vi I provided a few times and everything seems to work fine. If I come up with something, I'll repost. If you (or anyone) has an idea of what could be failing or if they've seen the problem, I'd appreciate a comment.
Thanks again,
Doug
Attachments:
Excel Fail.vi ‏15 KB

Report generation toolkit problem

hello everyone,
i am using Export waveform to Spreadsheet.vi for getting data into excel. i have downloaded and install the Report Generation toolkit 1.13 for make it working but still it seems not working
i am using labview8.6 on windows xp with Microsoft Excel 2003 .
i have tried the same vi on an other computer with same configuration and it works there, but not on my PC, i want to ask is there any thing wrong with my version and the Report Generation toolkit? or i am installing it wrong? or is there any specific folder or path i have to mention during installation of toolkit? if yes then how could i uninstall the existing toolkit because i couldnt find the installed toolkit path or location on my PC?
thanks
looking forward ...

Hi Hussain,
Are you still having these problems.
Can you use other functions in the toolkit or is it just that one.
Do you have other versions of labview than 8.6 intalled on your computer ?
/Christine

Error building .EXE Report Generation Toolkit

Whenever i try to build my application this error message shows up.... Error 1502 ocurred at AB_source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass: Save.vi
it says the possible reason is Word_Open_Document.vi
I'm using the report generation toolkit for office.... I really need to build this application soon!!
Please Help!!!
Thx in advance
Wong

I finally made it work... As a reference, i upgraded from labview 2011 due to windows 8 incompatibility, and found that the installer kept showing these error messages.
I read in another post that if you opened the troubled VI and just clicked on the property nodes to browse and then ok, you just saved the VI, restarted labview and the error message disappeared. To my surprise IT WORKED!!! I had to do it on several excell.llb VI's too.
Maybe you could report this bug in the report generation toolkit as a part of the NI team.
thanks!!!
Wong

Report Generation Toolkit does not recognize Office 2003

Hi there
The newly installed MS Office 2003 and LV 8.5.
When installing Report Generation Toolkit is screams that it does not recognize Office 2003:
"Microsoft Office version 2000 or higher was not detected on the system. You need to install Microsoft Office 2000 or higher before you install the NI Report Generation Toolkit for Microsoft Office 1.1.2."
What to do?
thanks
Pawel

Did you reboot your system after installing Office 2003? Have you launched Word and/or Excel since installing Office 2003? I think there might be some registry initialization that takes place on first launch of Word and Excel. If you've launched Word/Excel and the RGT 1.1.2 installer still isn't detecting them, there may have been a problem with your Office 2003 install. Try uninstalling Office 2003 and reinstalling it. When you reinstall, double-check that Word and Excel are selected in the install. Then launch them both a first time before trying to install RGT 1.1.2. If it still doesn't detect Office 2003, perhaps there's another problem with your system. Are you using any foreign language software? What OS are you running? Is it Office 2003 standard or professional? Is there anything weird about your Office install, like is it installed over the network instead of from CDs?
I'm hoping the answer to one of these questions helps you solve the problem. Keep me posted...
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

MS Office Report (Report Generation toolkit) is not executable, Xnode broken?

Hi, I am trying to generate an excel report, and I figured it would be easier to use the MS Office report VI, but I am getting the broken arrow saying the SubVI is not executable and that the library that defines the xnode is broken... here is a screensot attached, I already uninstall and reinstall the report generation toolkit and still the same... this is what I found on NI: "This error occurs when the library that defines the XNode you used is broken. To correct this error, reconfigure the XNode." but no idea how to reconfigure xnode
Attachments:
Error.png ‏67 KB

What version of LabVIEW are you using?
What is the nature of your Report? What should it look like? What kind of data should it contain?
Can you show us some code that you've tried to use? If so, include the code as either a Snippet or as a VI attachment (so we can plug it into our own LabVIEW installations and experiment with it).
I generally find that the Report Generation Toolkit is a very easy way to generate Excel Workbooks. I work primarily with LabVIEW 2012 and LabVIEW 2014.
Bob Schor

Report Generation Toolkit Installation

Similar Messages

Maybe you are looking for