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

Similar Messages

  • Error 7 with Report Generation Toolkit

    Hello Everyone,
    I'm trying to generate an Excel sheet report for some readings using "Report Generation toolkit" But when trying to generate the report, the report generation part of code is executed and gives Error(7) and there is no report is generated.
    The Code I use is atached in the following Link:
    https://www.dropbox.com/s/9n4brimucsd0xts/Report%2​0Generation.rar
    Can I get help please?
    Thanks in advance
    Solved!
    Go to Solution.

    I was able to download and open your compressed file.  I unpacked it into a folder.
    There are numerous peculiarities that lead me to ask "Are you trying to learn LabVIEW on your own, without a mentor and without training and guidance"?  Here are some of the things that I noticed:
    Although a Report Generation .lvproj, .aliases, and .lvlps file, the Project, when opened, was empty!  Since Projects were added to LabVIEW, almost all development should take place in a Project, but you do not appear to be doing so.
    You have an Event Loop (good) to handle pressing Start, Stop, and Report buttons.  But instead of using Boolean controls with a Latch property and using a "Value Changed" event, you use Switch Until Released (which, so far, I've never used) and a Mouse Down Event.  I suppose this could work, but I've never seen this pattern.
    You are writing an Excel Report, but are not using the Excel-specific VIs (such as Excel Easy Table).  Why (or Why Not)?  The basic idea of an Excel Report is that you create the 2D text data you want to write into Excel, then with a few simple VIs, you open Excel, write the Table, and save the Report.  In particular, you don't write out something that resembles the columns of the first few rows of a Spreadsheet (Date, Time, Test, etc.).
    Now to your specific question, Error 7.  Do you know what this error means?  If you click on Help, choose Explain Error, and put in 7, you will see this means "File Not Found".  Well, there is an obvious place where a File is used, right when your program starts.  I recommend that you put a Probe (do you know about Probes?) or an Indicator on the path going into the main For loop and see what File you are trying to open (hint -- there's an error in the way you build the path, but you should be able to figure out how to fix it).
    Good luck.  Hope these suggestions get you on a Better Path.

  • Ridiculous number of directories when build includes Report Generation Toolkit

    I was getting error 7 with the report generation toolkit, so I followed the steps here and it works. Only problem is, it makes a different support directory for each individual file in the NIReport.llb directory.
    The calendar and data directories are my own. The rest are the RGT.
    Help? haha.
    CLA, LabVIEW Versions 2010-2013
    Attachments:
    buildsetup.PNG ‏49 KB

    I set NIReport.llb to always included like it said, but it wasn't showing up after I did a build. So...I left it included always, I created my own destination with the same name (NIReport.llb) on the Destinations page of the app builder, went to the Source File Settings page of the app builder, selected NIReport.llb and set the location to be my NIReport.llb folder I created. I did a build and this solved the problem and all the NIReport.llb files were placed in a NIReport.llb directory. Someone pleaseeee tell me if there is a better way, but this will work for now.
    CLA, LabVIEW Versions 2010-2013

  • Application builder-Office report generation toolkit

    Hi,
    I remember there was a trick to get the executable work with different
    versions of Microsoft office but I cannot find it now. The problem it to get
    the exe work with some other office version that it was made. I use LabVIEW
    7.0 - 7.1 and Report generation toolkit 1.01 for Microsoft office. Was that
    possible?
    Thanks Eki

    Eki,
    When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work.
    Zvezdana S.

  • Error when using Report Generation Toolkit

    Hi, all,
    I am using Report generation toolkit to generate a report in either
    word or excel format. But i even can't run the "new report.vi". It
    returns an error code of "Bad variable type (-2147352568)", and seems
    this error comes out from the "call by reference" after the
    word/excel's "open VI reference". I have checked the folder
    "C:\Program Files\National Instruments\LabVIEW
    6.1\vi.lib\addons\_office", there are "_exclsub.llb" and
    "_wordsub.llb". The respect VIs are all inside. I don't know why there
    is such error. Currently i am using labview 6.1, Microsoft office 2000
    and Windows NT 4.0.
    Your kindly help will be appreciated very much!!!
    Thannk you in advance!! ^_^
    Your sincerely,
    celery

    So, if you place just New Report.vi on the Block Diagram, wire in the report type and run it, it gives you this error? Do the example programs which ship with the toolset give this same error also? If so, I would just reinstall the toolset first and see if that helps. It sounds like the entire install is corrupt.
    J.R. Allen

  • Word report generation toolkit error with Win 7 LabVIEW 2013, Word2010

    Hi All
    I'm seeing different Errors using the Report generation toolkit. Maybe you can help me with that.
    The errors are:
    -2147417846, application is busy in Word_Get_range.vi
    -2146824090 Exception in Microsoft word: Befehl misslungenHelp Path is wdmain11.chm and context ...
    -2147417846 application is busy in Word_Quit.
    the error messages are attached to the post.
    I'm testing 10 sensors with one application and want to run up to 5 applications on one computer. Since I'm seeing such errors as application is to busy I set all my report generation vi's as non-reentrant execution and additionally added some pause after each word modification.
    But I'm still seeing such errors when I run two applications on one computer.
    What is the best way to deal with these errors?
    thanks
    best regards
    Urs
    Attachments:
    exceptionerror.PNG ‏20 KB
    BusyActiveX2.PNG ‏20 KB
    BusyActiveX.PNG ‏22 KB

    Here my Vi's involved in creating the report.
    Is there a way to check wheter word is busy or already open?
    Attachments:
    save report as PDF.vi ‏26 KB
    create_report.vi ‏70 KB
    Word_Update_Table.vi ‏34 KB

  • 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

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

  • Report Generation Toolkit and Office 10 - build errors

    Using LabView 2011 and Report Generation Toolkit 2011.
    After installing Office 10, I would get build error for Excel-Print.Vi and Excel-SetCell.vi and build is then aborted.
    2011/vi.lib/addons/_office/_excelsub.llb/Excel-Print.vi.
    Says it is unable to save a vi without a block diagram.
    Uninstalled Office 10 and reinstalled Office 2003 and build went thru just fine.
    I can program using Excel 2003 and the compiled executable will work on another computer with Excel 2011 but once I install Office 10 on my LabVIEW computer I cannot build.
    Can't believe I could be the only one to experience this. Any workarounds?

    Duplicate Post

  • Error 10 when building an application in LV8 and Report generation toolkit 1.1.1

    I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
    Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
    Any ideas?
    Scientia est potentia!

    Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files?  I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs.  I think I've seen a similar post on the discussion forums in the past that recommended this.
    If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
    Good luck,
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • The report generation toolkit didn't work after the vi was build to an application.exe

    I write a VI using LabVIEW Report Generation Toolkit , it really works in the LabVIEW7.1 and 6.0 enviroment. but after the VI was build in to an application.exe, the LabVIEW Report Generation Toolkit didn't work even the application runs.
    thanks for your help.

    You might want to follow the procedure here:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
    (If the URL doesn't work, you can search for NI document ID: 2B87TVI8)
    Dan

  • 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 and Applicatio​n Builder

    I am going insane trying to work this out.
    I am trying to build an EXE program using Application Builder. The program uses the Office Report Generation Toolkit.
    I have tried including the dynamic VIs into the project, both from the Development machine and from the CD. I still have the same problem : the application does not start Excel. It is like the commands go into a black hole. There isn't even an error message.
    I have attached my report VI for you to peruse. Any help is appreciated.
    Brian Rose
    Solved!
    Go to Solution.
    Attachments:
    TestReport.vi ‏122 KB

    Yes, Labview 8.2
    Office Toolkit = 1.1.1
    I have tried many combinations of what files are included, from just the top level VI, to every VI in the heirarchy tree (a major pain). I am now trying to rebuild the project from scratch and see if that does anything.
    Brian Rose

  • 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

Maybe you are looking for

  • Mail crashes as soon as I try to open it

    Any help would be greatly appreciated! My roommate pulled out the ethernet cord yesterday to do some networking stuff on her laptop, and since then, Mail hasn't worked. The window will come up, but then it immediately crashes. I've: restarted ran Dis

  • IPod is recognized in Windows XP but not iTunes

    I just had my iPod mini replaced. When i connected it to my computer, it said "New Hardware Found" and recognized the iPod as an iPod. However, when I went into iTunes, it wasn't there, and the iPod Software Updater is up-to-date and says, "no ipod c

  • I cannot delete mail from my inbox and get a message saying (msg) could not be moved to the mailbox trash-POP account".

    I suddenly cannot delete mail from my inbox and get a message saying " (msg) could not be moved to the mailbox trash-POP account".  It does not matter if I am trying to delete a single message or mulitiple messages.  Can anyone help?

  • Number of current Requests in infoCube

    Hi, I looked into table RSREQICODS to determine the number of current requests in my infocube, but it seems like it has more that I know to exist in the InfoCube.  I only have data starting from 2008, but in the table when I specify the InfoCube I se

  • Error message after burning

    I keep getting an error message after I burn a song to CD, telling me it failed when it, in fact worked.  I have the latest iTunes software installed.