Filing of report generation error

Similar Questions

• Report generation Exe error

  Hello

  I use LV 8.6.1 with report generation tool 1.13 and I'm having problems to make my exe built to work.  I try to open an excel template and fill it with new data.  I broke the vi downwards to open just excel - open the template and then fill out some data.  But at this point excel opens not at all.  And of course, everything works fine in the development environment.

  Error code:-2147352573

  Member not found in NI_ReportgenerationToolkit.lvlib:

  Excel_open_workbook.VI

  NI_Excel.lvclass: new reportsubvi.vi

  I read a few pages of help that says Add LVclass and \vi.lib\utility\NIreport.llb directories in project folder and add them to the always include section of the build.  But no luck so far.

  Aside: the machine I want to use it on a 8.6.1 full which does not have the extra excel functions available my developer.  Is it possible to install the DEV report generation tool in the full version?  Then I wouldn't need to build an exe file.

  UPDATE: I just tried the exe on another computer that has a suite of Developer installed and it worked fine.  So I guess I need to know what I need to add to the building to make it work.

  Make versions of Excel are the same?

  Microsfoft has improved the ActiveX interface for each version so that the old instance didn't connect.

  Tone

• Report Generation Toolkit, production of the 2147417842 error, "The application called an interface that was marshalled for a different thread."

  Hello world

  I have an application that stores data in an Excel worksheet by using the report generation tool.  My VI have worked well in the past using Excel XP, but since I have upgraded to Excel 2007, I get COM errors like this:

  "2147417842 error occurred while the application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi', this is the exact wording, even with the odd punctuation and capitalization.

  The first occurrence of the error is not determined.  Sometimes, to the record 10 sessions, involving a new .xls file, may occur before this error.  Once this error occurs, I must leave LabVIEW to solve.  If I try to do something with Excel, I still get this error, even if sometimes it comes out different source Excel_Open.VI is another.

  These screw logging worked fine until upgrading to Excel 2007.  I checked and I have been using a very old version of the report generation tool, v1.0.1.  I read the documentation and had a big sigh of relief when I realized that I needed to upgrade to v1.1.2 for Excel 2007 help.  However, even after the upgrade, I still get the same errors.  I'm using LabVIEW 8.0.1 and I also build these screws in an application.   The error occurs in the application built both in the IDE of LabVIEW.  Anyone out there have any idea what I can do to fix this?  I google a bit and discovered it is a COM error, but I can't find any reference to the report generation tool specifically.

  Thank you

  Phil

  I think that suits him!

  Here's what I did: I left privileged execution environment level upper VI as "as the appellant.  I tried the "user interface" configuration, but it seemed to slow down considerably the program.

  Then, I found each sub - VI, calling the report generation tool and define the environment for running favorite "user interface".  All the errors went away, and the program is much happier now.

  Big assumption on what a Christian, thank you!

• error 7, report generation tools do not work after construction.

  Hello guys:

  only one problem. Help!

  I tried to build my programs with the application designer, application exe builded unluckly has no work well as before, I checked some similar post of this forum and added that NIReprot.llb in my project and rebuild, the problem is always held, my program add some text, tables and graphics in a word template with this report generation tools , but it always gives error 7 and ' NI_Word.lvclass: new report subVI.vi--> NI_report.lvclass:New Report.vi--> Report.vi new Creat->...' error information.

  is there anyone can give me some clues on this annoying problem.

  Thank you very much!!!

  zybear,

  Suggest you take the simple test vi and start adding all the features of your original application.  It accumulates in the stages and test at each stage.  I hope this helps you identify the problem.

• report generation toolkit VI error when running EXE

  A VI in the Report Generation Toolkit (version 1.1.2), Excel find Application Directory.vi, will not work correctly when you run an EXE file.  'Current VI course' block returns the path of the ongoing EXE rather than the path of the Application Directory VI find Excel.  (This would be true for Word find Application Directory.vi.)

  -Joel

  Have you had a look at this knowledge base article? The error is due to exclusion of all dynamics VI.

  Gregory C.

• Save the report that VI of report generation toolkit is broken

  Hi all

  I created a journal vi data, using report generation tools. He works first and then I copied the vi to another folder and tried to run but ended up with a broken vi.  The error occurs in the Save report vi of report generation package.   Please see vi and captures screen attached. I'm sure that if you run the vi, it might work on your machine, but will not work on mine. That's why I find it cable. Has anyone seen this kind of problem before?

  Hi all

  I spoke with an application OR engineer and we have tried to compile mass of Labview on the particular folder containing the VI.

  Tools---> Advanced---> massive compilation.  This corrects the problem.

  Thank you

• Report Generation Toolkit compatibility with Microsoft Office 2013 and LabVIEW 2011

  Hello

  I design the 2011 Version of LabView to test solid state device and need to create test data after this unit tested.

  When I save the test data in the configuration of Excel after you run the Laview program, it created an error like "error - 41007 is is produced in NI_report.lvclass:New Report.v->... OR reports; Musr you have the LabVIEW Report Generation Toolkit for Microsoft Office installed to create this type of report. The musr toolkit also have an activated license or be in trial mode. »

  Questions: Do I need to install LabView Report Generation Toolkit for Microsoft Office on my computer? If Yes, what is the LabView Report Generation Toolkit for Microsoft Office Version. Where can I find this software?. I use Labview 2011, Windows 7, MS 2013 in the computer.

  Thank you

  Jonathan Tran

  You can try this: http://download.ni.com/evaluation/labview/ekit/other/downloader/2011RGT.exe

  From this link: http://download.ni.com/evaluation/labview/ekit/other/downloader/

• VI LabVIEW Report Generation Toolkit elements in a TestStand sequence does not work with a LabVIEW 8.5 run-time engine

  Hi all

  I'm using LabVIEW 8.5.1 and TestStand 4.1. I did a sequence TestStand with a VI in this document, which uses items Report Generation Toolkit. On my machine I use LabVIEW and TestStand development system license. On another machine I use TestStand with basic deployment license and I chose the LabVIEW 8.5 run-time engine in the Configuration of the adapter. Everything works well except this VI with elements of Report Generation Toolkit. The error message shows that the VI is not executable. It works well only after I installed with a trial license and selected LabVIEW LabVIEW 8.5 development system in the Configuration of the adapter.

  I found other posts and a document in the knowledge base with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument but I am not no EXE files in my sequence, so I do not know how to fix mine. Someone has an idea?

  
  

• Cannot print on the Epson TM - U590 Slip printer Report Generation Toolkit with LabVIEW 8.6.1

  Hi all

  I have an application that uses the report generation tool to print tickets for a printer file.  Usually, it works very well - I 8 existing facilities where there is no problem

  I install the software on a new site that uses a printer Epson TM-U590 slip currently and I can't for the life of get me printing to work

  Using a Standard report, the Print Report.vi returns error-41002, indicating it does not find the printer.  I opened the VI using the remote debugging and it does not find the name of the printer properly with the available query Printers.vi.  It gets an error-2147352567 code starting from the printed node, which is then replaced by the de-41002 error that is reported.

  For historical reasons, I always use LabVIEW 8.6.1 for this project.  I plan to spend in 2011 or 2012, but I had some reliability problems with the other parts of the application after trying to upgrade to a new version of LabVIEW, so I would avoid it at this point.

  The application runs on a standard desktop with Windows 7.  The slip printer works fine if I print from Notepad, and my request is happy to print to any other printer, just don't slip printer.

  The slip printer using the LPT port.  Previously, printers of the folder that I used were USB but I expect the printer driver to hide the details of the application...

  Any ideas would be very appreciated

  See you soon

  Brett

  I managed to solve the problem, thanks to this article: http://digital.ni.com/public.nsf/allkb/67D60209102E2161862568AC0074BF64

  I now have the same problem with a folder of Star printer (a TUP592), this time with another program developed in LabVIEW 2011.

  As mentioned in the article, the problem is in fact to do with margin settings rather than the name of the printer, despite what says the error message

  After some tests, I received the Star printer to work by setting a large (> 14cm) right margin.  No idea why this is necessary because it seems quite happily print to the right edge of the paper, but there you go.

  So I don't have defintely solved the original problem yet, as I've not had back on the site, but I hope that it will be useful to someone else.

  See you soon

  Brett

• Exe version with database conn and report generation vi?

  I tried to build a .exe and learned the hard way that there are a lot of things had to be included to make this work.  As it is now my program does not work.

  I wanted to get a list of the steps needed to make a successful build.  Please correct me if I'm wrong or missing something:

  1. for report generation tool, I include some files support (_exclsub.llb and _wordsub.llb)

  2. for database connectivity: I had to follow the user's guide of OR by implementing the generation of script function to tools?  Is there an easier way?

  If there are no more simple ways to get this working please let me know.

  Machine of dev = LV2010 office 2007 vista

  Target machine = XP office 2007

  Thanks for the reply,

  Yes, I have the runtime installed.  I had also the program works correctly by following these steps:

  --> LV 8.6 and higher

  1 added two files to the project in the Project Explorer menu.

  a. file utilities

  b. record of LVClass

  2. during the build of .exe I had to:

  a. Add a folder of LVClass to always include in the source file settings

  b. navigate to the Utilities folder NIReportLLB folder and add that always include as indicated more high (Note: If you add all the utilities folder you will get an error vi broke during construction, even if set you the vi it does still not work for me so I just included the file I need to word/excel)

  has took about a day to troubleshoot and fix, but the program works as expected.  Hope this helps someone else in the future.

  Bernie

• Report generation-> generate an exe from a PC with different Version of Office

  Hello

  I want to build an exe from a VI that use Report Generation Toolkit. The application must be deployed on multiple PCs using Office 2000. During the development phase, I installed Office 2000 on my PC, and everything was ok. After that I was with her, I have reinstalled Office 2007. The Report Generation Toolkit to my PC is so for Office 2000 (it was installed when I had Office 2000 on my PC).

  These days I had to fix a few bugs in my application, I did a new exe but the part that generates the Word reports (using the GTA) doesn't work anymore - I received this error with-35... 9935 (or something like that).

  I tried to find the problem and I found this: with exactly the same VI (_Word dynamic VIs.vi - for Office 2000) nodes invoke from a PC with Office 2007 and Office 2000 PC look different. For example, in Word_Open_Document.vi, the node to invoke Document is different for a PC with Office 2000 + GTA for the year 2000 and a PC with Office 2007 + GTA for Office 2000 (no error).

  So, I tried to copy the VI from a PC with Office 2000 + GTA 2000 on my PC but I can't build it because I get the error: there are a few errors in dynamic VIs.vi _Word (invoke nodes do not match).

  Finally, my question is: How can I build the exe on my PC: 2007, but with GTA for Office 2000 Office?

  Thank you

  Paul

  Hello

  Thank you for your advice. Can you please tell me what you mean with the envelope vi? I don't really understand what you mean.

  Furthermore, I solved the problem. I discovered that the nodes invoke are updated based on the object library for the ActiveX control (in this case the MS Office). The data types are store in the msword9.olb (version 9 - for office 2000 in the Office folder) and msword.olb (version 12 - for office 2007 also in the Office folder). I tried to save the msword9.olb (using the regsvr32.exe) but it does not work for olb files - I need the ocx or dll. But, if I can replace the msword.olb since Office 2007 Office msword9.olb 2000 everything works.

  OK, measures that need to be made:

  1. install the GTA for Office 2000 on the PC

  2. DON'T change anything in the VIs.vi _Word_Dynamic. When Office 2007 is installed the VI arrow should be ventilated (error in VI)

  3 copy the msword9.olb for a system with Office 2000 (or your version) and copy it to your system with Office 2007 with the new name msword.olb. Are NOT FORGET to make a backup of the original file to MS Office 2007 and handing it to the end.

  4. once the new msword.olb is there, the VIs.vi _Word_Dynamic should be no error

  5. build your app exe

  6. restore the old msword.olb

  7. ENJOY your life!

  I hope that it is also useful for someone else.

  Paulie

• Report Generation Toolkit missing VI

  LabVIEW version 8.6.1

  Report Generation Toolkit 1.13

  I just started work on an ongoing project that others have contributed to during some time.  (This is why the project being in older versions of LabVIEW)

  On my PC, apparently miss me VI "Word get ActiveX References.vi"

  I have the version 1.13 of the installed tool, just like all other machines running this code performs.  But my word.llb only contains VI

  I tried to copy just that VI in the .llb the VI is then found by the application.  But is not executable due to this error: this VI is related to a library that does not include the VI. The VI may have been removed from the library. ' Add the VI to the library or select file "unplug library.

  I also tried to replace my C:\Program NIUninstaller Instruments\LabVIEW all 8.6\vi.lib\addons\_office\ the directory with the files from a PC that worked.  Yet once, I get the same error as above.

  I tried to do a repair on my installation of the box tool.  But as far as I know, it did nothing.

  I also tried just reinstalling the Toolbox.  But since that it has been already installed, it did nothing.  I would hesitate to uninstall and reinstall the Toolbox for fear of breaking all my 8.6 projects, as well as perhaps my 2009 projects.  I don't think that he messes with my 2009 installation.  But I know the order in which things are installed can be critical in the system with several versions.  I don't know if this applies to tool boxes or not.

  This PC also has a LV 2009 SP1 installation, and this version also has the Report Generation Toolkit installed. (even if it is a different revision of the Toolbox as 1.13)

  I know that in the past, several versions of this toolbox were not compatible, which means that a single version of LabVIEW installed might have a job Report Generation Toolkit installed.  But I have been in agreement that it was no longer a problem.  Although it may not be a coincidence that none of the other boxes development runs this code are not installed LV 2009 have.

  Anyone who has encountered a similar problem and found a solution?

  Thank you.

  Before that we unified the version numbers of LabVIEW and toolkit (in 2009), there are cases where it has not changed the version number in the registry for one reason or another on a minor update.  So very well may have installed 1.1.4 and it can still say 1.1.3.  However, assuming that 1.1.4 has been installed, I can't imagine any reason why Word get ActiveX References.vi wouldn't be here.  VI lives at vi.lib\addons\_office\word.llb, so after installation from 1.1.4 to your folder of LabVIEW 8.6, check that the VI is actually there.

  D

• Report Generation Toolkit V9.0.0: Report.vi print does not print

  Hello

  I migrated my project Labview 8.5 Report Generation Toolkit V1.1.2 to Labview report Generation Toolkit V9.0.0 2009 system.

  In this project, I use the report generation tool to print a Standard report with e bit of tables and graphs.

  The Report.vi of printing VI now offers the 41002 error with the text "invalid printer name. I, of course installed the right printer on the machine.

  I Don t one connection at the entrance of 'Printer name' string of VI, because I want to use the default printer.

  In my opinion, West one bug in the Report.vi of printing: If you don t the "printer name" input wire, the vi must use the default printer, but in this case the vi connects the entry blank chain at the entrance of the node method he calls.

  I fixed this bug, but the node method always returns the same error.

  any ideas?

  Thank you!

  Thanks for the link!

  For some reason I can´t find this specific article in the knowledge base (my browser is rerouted always to the German of ni.com version, because I'm in Austria). I tried to search for the exact title of this article and the error message string, but no result...

  I also installed Labview 8.5 and the toolboxes 'old' on my new computer in addition to Labview 2009 and the 'new' toolboxes and tested my program to 8.5. Here, I got an error mentioning the margins and I had to change the margin for printing settings, then worked.

  After reading the article, I applied the same changes to the margins in the 2009 version of my program and it works too!

  Problem solved!

  Thank you very much!

  PS:

  I wrote first of all, that West might be a bug in the new version of Report.vi printing, but I ve compared to the old version and there seems to be no bug, sorry!

  After all, I decided to stay with Labview 8.5 for now, due to another problem:

  It s not possible to "save the previous version" of LV2009 to LV8.5 directly.

  Laview grave failure, when a VI contains a structure of the event I found by looking in the "known issues", and I have a lot of report with the structures of the event!

  I must have the ability to save my projects Labview 8.0 and 8.5. The only way is to save for 8.6 and then save 8.6 to 8.5.

  That s long and nasty!

  Perhaps a future update will solve this problem (without producing new)

• LV Report Generation Toolkit for Microsoft Office said "this VI or element belongs to a library that has expired or improperly licensed."

  I downloaded the LV Report Generation Toolkit for Microsoft Office for evaluation with LabVIEW 2010. Examples to help get a lot of errors, including "the Subvi is not executable. You must fix any errors in the Subvi before this can run VI. "and"this VI or element belongs to a library that has expired or improperly licensed. "

  I decided that I wanted to evaluate the Toolbox instead of putting an activation code during installation. Installation went well.

  How can I get the examples from this LV package to run so that I can evaluate it?

  A computer restart was costing the day the day to solve the problem.

  Installation of the toolkit does not have a reboot of the system, but it seems to need i.

• Report Generation Toolkit and Application Builder

  I'm going crazy trying to get out.

  I am trying to build an EXE using Application Builder program. The program uses the Office Report Generation Toolkit.

  I tried including the dynamic screw in the project, the computer development and the CD. I still have the same problem: the application does not start Excel. It's as if the commands are going into a black hole. It's not even an error message.

  I enclose my VI report for you to view. Any help is appreciated.