Report Generation Toolkit Print HTML Problem

Hi,
i have a problem printing a html Page at a Costumers PC with the Report Generation Toolkit.
I use LV 2012 and the Report Generation Toolkit in 32Bit Mode.
The Target is a Win7 64Bit Machine with IE10 of our Customer with very strong security rules.
Our Programm generates a HTML Repor which is saved without any problem.
When i then try to print it with Print Report.vi it doesent work and i get error1 out of the SubVi NI_ReportGenerationCore.lvlibrint HTML Report using IE.vi.
This Sub.vi simply cant open the HTML Page with the IE.
I think its the costumers Security Rules that cause the Problem.
I saw a very strange behavior of the IE.
When i double click the .html file the IE gets opened and displays the file properly.
When i then hit the reload button it also gets reloaded.
When i click in the browsers adress bar and hit enter (Which normaly does a reload) i get an error "Adress Bar, Adresse, access denied".
And i think that happens in the Sub.vi.
I talked to some friends an they sad it could be that double clicking and reloding is done with the local user an the clicking and hitting enter reload is maybe the systemuser.
So i asume that the Sub.vi is also using the systemuser.
How can i determin which user is used to execute a vi?
Can i influence the user?
Has anybody a solution and seen this problem?
Regards,
westgate

If I understand your situation correctly, you are able to use the LabVIEW Report Generation Toolkit to create an HTML report, which you save as an HTML file. Can you open it in a browser and print it using the browser's Print button? I've use LabVIEW to generate HTML reports, but have never tried to print the Reports in LabVIEW -- I've always used the "browser route", myself.

Similar Messages

Report Generation Toolkit - Prints data from a previous report in Word

I am running an executable from the "system exec.vi" created with Labview 6.1. I am using the Report Generation toolkit vi's to create a report in Word that prints simple Title with test header and then appends a Table with measurement data. The problem is the measurement data in the table is from a previously printed report. This problem only exists when I Run the Report.exe from the "System Exec.vi". If I manually start the Report.exe in Windows or open in the Windows Commandline the correct data measurement data is printed in the report table. Any suggestions are appreciated. Thank You

Hi,
So far I havent been able to reproduce this on my computer. Could you post your code so that I can try and reproduce this issue?
Feroz P
National Instruments

Report Generation Toolkit, Print Excel Report, LabVIEW Crash

Hello,
when printing a report generated with the report generation toolkit for excel my build application crashes on our customers PC.
When I run this application on my PC it works fine.
The problem is the active X invoke node that trys to print the report but i cant get any error messages to find out where to locate the problem.
Maybe that there is a problem with the active X node or the Excel Version on the customers PC?
I use LabVIEW 2010 and Excel 2007 the customer has Excel 2003 SP 3.
I changed the report to generate it in Word where the Print_Report.vi fine on both PCs. But in Word Report there is called another active X invoke node to print the Report. So it seems for me that there really is a problem with the Print in Excel active X invoke node.
Mybe someon can help me in finding out whats the problem.
Greetings Daniel.
Solved!
Go to Solution.

Hi Daniel,
your behavior has been reported by others. For example:
Application Build Failure on Excel.Print Report call
http://forums.ni.com/t5/LabVIEW/Application-Build-Failure-on-Excel-Print-Report-call/m-p/1563242
Problem posted: 05-17-2011 02:19 PM
Workaround posted: 06-01-2011 and later
So their workaround was to use Excel 2007 or 2010 instead of 2003. Is this working for your customer?
Best Regards,
Jan

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

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)

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

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

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

Problem building application using Report Generation Toolkit, LV 2011

I'm using LabVIEW 2011 under Windows 7.
I tried to use Application Builder to create an executable from a large body of code. One thing the application does is load VIs into a subpanel and run them.
Application Builder created the executable and gave no error message. The built application ran except that it couldn't run any of the dynamic VIs.
I finally succeeded in doing a screen grab on a transient dialog (about 1/10 sec. appearance). The dialog showed an attempt to load <vilib>:\Utility\NIReport.llb\NI_report.lvclass.
In one dynamic VI I commented out the call to the only VI that uses the Report Generation Toolkit (called only from dynamic VIs, all of which call it). Sure enough, when I built the application with that change and ran it, the dynamic VI that didn't invoke the Report Generation Toolkit did successfully load into the subpanel and run.
So, trying to prove to myself that that was the only problem, I wrote a VI that does nothing but load a VI into a subpanel and run it. User can choose one of two VIs: one that doesn't call the Report Generation Toolkit (or do much of anything), and one that does. Both VIs run fine standalone.
The not-much-of-anything VI loaded and ran in the subpanel. The other VI didn't--the same dialog, mentioned above, popped up for 1/10 second or less. Screen grab is attached.
When I included LVClass and NIReport.llb folders in the project (from vi.lib\Utility: Snapshot folders), and "Always Included" those folders (per a suggestion on this forum from a few years ago), the result was the same. The result was also the same when I included either one of those folders but not the other. Likewise it doesn't matter whether I add the dynamic VIs as "Always Included" or not.
Another piece of information that may be pertinent: when adding the NIReport.llb folder, I got a message that it was impossible to add a certain VI that's part of some report-type class, because a VI of that name already existed in the project. Screenshot of that dialog is also attached.
VIs and project file are also attached along with the two screenshots. I hardcoded VI paths, so put everything into C:\Testing if you want to see what the code does--or hack as desired, etc.
I will be deeply grateful for any help! And I apologize in advance if there's already some exact or close-enough solution posted--but I doubt there is. I looked around.
Thanks very much,
mws
Attachments:
Test-App-Build.zip ‏336 KB

Hi again,
If you extract all files in the original zip attachment to a folder called C:\Testing on a Windows 7 machine running LV 2011, and then use the build script within the project file to build the application, you can run the application and see what happens. You can also play around with the build parameters, rebuild, run, and see what happens then. You can also open my VIs and see what I'm doing.
The application lets you pick one of two dynamic VIs to run in a subpanel. One VI contains calls both to Report Generation VIs and some functions from the Advanced File Functions palette. The other VI does not.
When you pick the first VI to load and run (the one with the Report Generation and Advanced File Functions calls), it loads into the subpanel but is not executable.
When you pick the second VI to load and run, it does load into the subpanel and execute. So there's nothing wrong with the way I load and run a VI in the subpanel.
In the development environment, the whole thing runs with no problems.
Evidently the built application has problems resolving paths of something called by Report Generation VIs and by the Advanced File Functions I use.
I've done a lot of experimenting and no luck. I've looked in forum archives, etc. etc., for possible solutions. I'm hoping there's some simple solution I've missed.
Thanks very much for any help!

Problem with Reporte Generation Toolkit for Microsoft Office 2010

When I use the Report Generation Toolkit (LabVIEW 2010), and Office 2010, the tables generated are bad.
In office 2007 in the tables are correct.
Someone can help me solve this problem?

The solution referenced in your post does not actually workas far as I can tell... at least for LV2011 and Office2010 on Win7
Am I missing something here?
Attachments:
Testbench_ReportGen Table_BUG.vi ‏10 KB

Problem writing to excel file using report generation toolkit

hello everyone, i have this report generation toolkit... and i want to output DAQmx Analog I/P data on to an excel sheet. the DAQmx is programmed to collect
data at 3samples/sec. however, when i see the excel file that Report Generation Toolkit generates, the time stamp is updated every second instead of every 0.33sec.
can anyone please help me? i am using the MS Office Report Express VI.
Now on LabVIEW 10.0 on Win7

@All, I got rid of the express VI, decided to work on the custom low level VIs instead. however, i have a new problem now...
I have a case statement wherein, the user selects if he wants to start generating a report. once the program enters tat loop, the program speed reduces!
can anyone please tell me why is it happening? i ahve attached the vi... also another question.. in this VI, i am capturing the unwanted data into the graph as I am indexin the graph input. how can i make a logic
that the graph captures the data only when I am switching the CREATE REPORT button (which is in the while loop). is there a way that I can append the data to the graph without creating a new graph every iteration? please let me know
thanks
Now on LabVIEW 10.0 on Win7
Attachments:
Untitled 7.vi ‏75 KB
Untitled 7.JPG ‏99 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

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

Office Report Generation Toolkit 1.0.1 and MS Office 2000 problem

Hello.
I'm tring to make a repot in word using a template..everything works just fine when in development..but when i make the executable the problem arises.
I get error code 7 (Cannot open vi reference) in NewReport.vi.. FYI i'm running the aplication in the same machine i'm developing.
I'm sure everything else is ok..- changed paths to work in executable, template in correct folder...i'm adding the necesary support llb to the executable(Win200), etc - ..i tried reinstaling office and the report generation toolkit but i still have the same problem...
How can i solve this?....
Thanks in advance for all yur help.

Well..that was a very good answer to my question...and it solved my problem. Thank you.
I thought that by adding just the llb as support files would be enogh..but now i see this is not correct..thanks again.

Problems in using Application Builder to Build a exe file with Report generation Toolkit

Hello,
It's my first time to build exe. But I have Problem when the VI have Report Generation toolkit VI.
It's no problem in VI Format , But It can't work when I build as EXE format
Can Anyone help me, and state step clearly in how to solve the problems?
Thank you!!

If the code works OK in the development system but not in an executable there are a few things you can check. The two most likely causes are:
There is an error occuring that your code isn't reporting.
There is a file path that under the executable isn't valid.
First make sure that all the error clusters are daisy-chained together in the subVI that you wrote to create and populate the excel file. Next make sure that the end of that chain goes to an indicator on the VI's front panel.
Second, make sure there are indicators on other key parameters like the path the file is trying to write to.
Third, temporarily modify the VI properties of that excel IO VI to open it's front panel when called, and rebuild your application. The next time you run the application the front panel will open when you try to write to the excel file and you should be able to see what is happening.
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

Report Generation Toolkit Print HTML Problem

Similar Messages

Maybe you are looking for