Erreur 2147352567 avec Toolkit Report Generation

Bonjour,
Je dois programmer la génération automatique d'un rapport sous Excel. Je possède le Toolkit Report Generation.
Tout fonctionnait correctement jusqu'à ce que je reçoive le message d'erreur "2147352567" en executant le vi permettant de générer mon rapport.
Ce message survient dès l'utilisation du sous-programme NewReport.vi .
Lorsque je cable entrées et sorties d'erreur, cela m'indique le message suivant: Nœud de propriété (arg 1) dans NI_ReportGenerationToolkit.lvlib:Excel_Open.vi->NI_ReportGenerationToolkit.lvlib:Excel Try Opening Excel Again.vi->NI_Excel.lvclass:new report subVI.vi->NI_report.lvclass:New Report.vi
Merci d'avance pour votre aide.

salut j'aime bien utiliser le report generation toolkit.
A la lecture de ton post; je suis étonné par l'erreur; en effet
et
si je lis ton message, l'erreur provient de Excel_open.vi
Donc ouverture d'excel OK; mais erreur "-2147319784
J'ai le sentiement qu'Excel est dans une apparence que l'ActiveX n'arrive pas à modifier.
> Tu peux laisser le vi ouvert, et regarder les valeurs des paramètres d'entrées
> tu a redémarré ton PC?
> Excel est bien fermé? plus de process ouvert? ctrl + alt sup
> Faire un exemple
A+
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

Similar Messages

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

Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

Hi all,
I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
I have made some steps, like "Open Workbook", "Write Data", etc.
My steps run well, excepts one step : "Close Workbook".
If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
I feel that I'm trying to use a reference which has been killed in the "Stop" step...
I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
Thanks,
Callahan

Hi Callahan,
SignalExpress (SE for short) does the following on the Stop event:
1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
3. The VI is then run, with those values and states.
4. SE checks to see if any errors where returned.
5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
Hope that helps. Feel free to post your LLB if it doesn't.
Phil

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

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

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

How to obtain the table index in word use LabVIEW Report Generation Toolkit for Microsoft Office

I created a word templete and it had several tables. When I use the "Word Edit Cell" function in LabVIEW Report Generation Toolkit for Microsoft Office, the function need "table index", and I didn't find any function to get or set the table index in word document. How can I achieve my attention to write value to specified table cell using the "Word Edit Cell" function?
Thanks for reply!
YangAfreet

Hi yangafreet
You do not need to get the table index for the word edit cell.vi from anywhere. LabVIEW will automatically index all the tables in the document. See the attatched vi for an example.
Rich
Attachments:
Table Edit.vi ‏23 KB

Report generation toolkit excel, decimal?

Hello!
I have problem with the report generation toolkit excel!
I only gets 3 decimals in excel?
Ex. In labview = 0.0458943 when i send it to excel = 0.046.
I use Excel easy table.vi to transfer my array, should I use someting else?
Ive already tryid to increase the decimal in excel but i doesent work.
Labview 8.6
Report generation toolkit ev 113

Johan1300,
It sounds like you are writing a 2-D Array of doubles to excel. The Excel Easy Table.vi converts numerics to strings before writing data to excel. It is written to always use 3 decimal places. You need to convert your 2-D array of doubles to strings before writing the info to excel. Here are a couple of ways to make the conversion. The top method is based on how the Excel Easy Table.vi makes the conversion. Note that in both examples the format string constant sets the number of decimal places to 8.
Message Edited by Wayne.C on 04-08-2009 09:12 AM
Attachments:
2D Doubles to 2D String.png ‏6 KB

Erreur 2147352567 avec Toolkit Report Generation

Similar Messages

Maybe you are looking for