Report generation toolkit (1.0) can't be installed under LabView 6.1.

When installing the toolkit, it showed that it was unable to locate the LabVIEW run-time engine of version 6.0 or compatible. However, my computer has already installed a run-time engine 6.1 (I saw it on my control panel->Add/remove programs). Do I need to install another run-time engine 6.0?

Hello William,
You may want to see this article on NI.com. It sounds like it addresses your particular issue.
Regards,
Chris J
Installation Errors with the Report Generation Toolkit 1.0 for Microsoft Office and LabVIEW 6.1
http://digital.ni.com/public.nsf/websearch/BEE4820C6BB7305186256B42005C9514?OpenDocument

Similar Messages

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 Table Row Height-MS Word

I am having trouble setting the table row height in the report generation toolkit. I can set the column width fine, but the row height seems to remain the same no matter what I set it to. I have attached the VI that generates and formats the table, and the printout it is resulting in. I have also attached the template file I am using.
Any tips to get this to work right? I am trying to make the cells exactly the same height as the text inside.
Solved!
Go to Solution.
Attachments:
AddMarkersToReport.vi ‏20 KB
badFormatting.pdf ‏179 KB
splitter.docx ‏13 KB

Hi,
So I tried .2 and it didn't work. So I went to Word to manually change it, and it did not work either. There is a selection box in word, for the table properties, that seems to default to the value "at least". When I changed this manually to "exactly" in word, no problem with the .2 manually in Word.
Hopefully this can be set within the template, for all new inserted tables. I'm not sure the report generator VI's expose this property. Well, this is a start for the issue.
Edit ****
You can go into the add table VI and expose the property. See pic. However, you have to decide if you want to "upgrade" this VI permanently to expose this property or make a copy with the property exposed. I haven't messed with the new class reports too much, so not sure of the ins and outs with this.
I think this is the issue with the row size becoming smaller.
Mark Ramsdale

How to get data from an existing Excel file using report generation toolkit

I'm trying to use the Excel Get Data vi from the report generation toolkit, but i can't figure out how to turn a browsable path into the right type for the VI. I've tried using the New Report.vi, but that doesn't work unless you use a template. It won't open an existing excel file and make it an open report to pull data from.
Essentially, i have a bunch of excel files that have data in them and i want to use a VI to analyze the data. So, i'm trying to pull in all the data directly from the excel file so i don't have to reproscess them all into text so i can use the more standard spreadsheet VIs. But to even convert the excel file programtically in labview won't i still need to be able to open the excel file and get the data?
Solved!
Go to Solution.

I C.
Got it,
the reason why I can view it using my Excel file because its in .CSV.
I open Microsoft Excel to open .CSV file.
But you can also open .csv file with notepad.
So, you cannot open .xls with Read Spreadsheet File
I learn something everyday
Best regards,
Krispiekream

Problems creating a web service that uses the report generation toolkit

Hi,
Im trying to develop a web service using labview 2013.
I create a html form that is correctly communicating with my labview method and part of the web service functionality is to create a report from the data obtained in the html form published.
I realized that using the report generation toolkit inside of the web service method the server cannot generate a report. ( If I run the same Vi before publishing the web service it works on the server but it doesnt work after I deploy it)
I thought that maybe Im unable to use the report generation toolkit VIs inside of the web service because Im not incluiding the (dynamic VIs labview uses when they run), I tried to add the excel dynamic library to the proyect but with no success.
I also tried to use VI SERVER to call a VI that generates the report using the report generation toolkit in the method that runs when the web service is call but it doesnt work either.
How can I deploy a web service able to use the report generation toolkit ?, how can I deploy a web service able to use VI server ?
Any help is really appreciated.
Erwin Franz
Erlab

The issue you are running into is actually a limitation intended by Microsoft. They don't want windows services to be able to call into the ActiveX interface for Microsoft Office for security reasons. If you are deploying your web service to the NI Application Web Server on Windows you will run into this problem since the web server is a Windows Service.
While I haven't tested this, you may be able to work around this by packaging your Web service with a LabVIEW EXE rather than deploying to the NI Application Web server.
Mark
LabVIEW R&D

Remove worksheet VI - Report Generation Toolkit (LabVIEW 8.6)

Hello,
I am using the Report Generation Toolkit that ships with LabVIEW 8.6 for creating an Excel report. I am looking for a way to delete spreadsheets in a workbook. I did come across couple of message posts in the forum which mentioned about worksheet removal using some VIs that were shipped with previous version of LabVIEW. I could not find the built-in VIs in newer version of report generation toolkit (the one with LabVIEW 8.6).
Is there a way I could remove worksheets in LabVIEW 8.6?
Thank you.

Assuming you're using Report Generation Toolkit 1.1.4 with LabVIEW 8.6, you can use the following VI (in the Report Generation > Excel Specific > Excel Advanced subpalette) to gain access to your current Worksheet and/or Sheets object:
Note that this VI is not available in Report Generation Toolkit 1.1.3.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

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

How can I create a Report with the Report Generation Toolkit?

Hi,
I have installed Labview Report Gerneration Tool for Microsoft Office Version 1.1 and now I want to use MS Office Report Express VI but it need the VI "Dflt Data Dir.vi". I don't have this on my computer, why? Where can I get this VI? Can somebody help me?
thanks Labprog

Hello Labprog
This VI should be located in the file.llb in the folder
..\vi.lib\utility. Thus, it is not part of the report generation
toolkit but of LabVIEW. I am not sure why you are missing that file on
your PC, maybe you just did not find it because it is hidden in a LLB.
Maybe this LLB is not part of your LabVIEW package (Base, FDS, PDS).
Anyway, I'll attatch that little VI, hoping that this is the only one missing.
Ingo Schumacher
Systems Engineer Sound&VibrationNational Instruments Germany
Attachments:
Dflt Data Dir.vi ‏11 KB

Can i open a existing report using a report generation toolkit

Hello All,
Suppose I create a new excel report today and close the program, Tomorrow I open the same program and instead of creating a new excel file, i need to update the test results data into the excel file which was created yesterday, is this possible.
I am confused because there is no option called Open report in report generation toolkit, it just has create new report option.
Probably NI Guys can work on this...sorry if it is a;lready existing?
Is there any method to open a existing report?
Pls help.....
Thanks
Solved!
Go to Solution.

Hi,
I have a similar problem. I'd like to use Report Generation Toolkit to enter data into some cells in the active worksheet of the active workbook but it seems impossible?! The user has in beforehand opened the desireed workbook and activated the desired worksheet. I use the 'New Report' VI with the template input set as the path of the active workbook (some self-made ActiveX calls to get the path). When this VI is run, howevere, the excel file is sort of re-opened and another worksheet becomes the active one.
I tried to make a customized copy of New Report.vi, New Report subVI.vi and Excel_Open_Workbook.vi so that the Report object works with the currently active workbook and worksheet, but I failed due to my lack of knowledge in LV classes and such things. It would've been an ugly solution anyway to have custom low-level VIs that does not follow when the RepGen Toolkit develops in the future.
Best regards,
Andreas Nilsson

Can I align the orientation of axis labels in a graph generated with the report generation toolkit (Word)?

I was wondering how to align the axis labels, i.e. 90 degree or such when creating a graph with the report generation toolkit in word.
I can do it after the document is created through Format axis title -> alignment but is there a way out of LabVIEW?
I'd especially like to rotate the y-axis label by 90 degrees.
Thanks a lot,
Juergen

I think he means he can modify it by hand after the report has been generated... But what I want to do is generate the word graph out of labview already with the rotated axis label...
After I posted this I found out that we can do this with a macro and use it from labview, but unfortunately I don't know VB, or VBA...
Like this:

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

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

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 (1.0) can't be installed under LabView 6.1.

Similar Messages

Maybe you are looking for