EXCEL fails to Launch w/Report Generation Toolkit LV6.1 from a Built Application but works fine in full version

In my developer version, I can generate reports that load up Excel and put the data in. When I build an application, it won't work. I don't get any errors and the code executes, but excel doesn't launch. I have the correct _excelsub.llb file for WindowsXP. It worked fine in Labview 6.0, but the same bld script with the new _excelsub won't work.

You may want to try creating executables of one of the Excel example programs that comes with LabVIEW and see if they exhibit the same behavior. That will tell you if it's your code or something more specific to LabVIEW itself.
J.R. Allen

Similar Messages

  • How to update data to excel in runtime with LabVIEW Report Generation Toolkit

    hi,All
         i am using LabVIEW Report Generation Toolkit,and a newer.i want to insert the data in excel for every loop.
         so at first,need to creat a excel file(xxx).and when every loop end,the test data can be insert into the file(xxx).when the test finished,the file will be saved.
         i have seen the examples in LabVIEW Report Generation Toolkit, all of them need to creat a new file.i need update the data in the same file.
         can you give me some advances for that?
         my labview's version is 8.5 and LabVIEW Report Generation Toolkit's version is 1.1.0.
         thanks a lot.

    Hi cat099,
    One question, why don't you store data of each loop, say in shift register and update all data in excel  at once when your test is finished.
    It will be easy. Or else, if you want to build same functionality as you mentioned, then you can build your own vi to write in excel. No need to use report generation toolkit.
    See attached example.
    Gaurav k
    CLD Certified !!!!!
    Do not forget to Mark solution and to give Kudo if problem is solved.
    Attachments:
    write to excel.vi ‏21 KB

  • Hide Excel Chart Legend Using LabVIEW Report Generation Toolkit or Active

    Hello Eveyone:
    I work on the report generation toolkit in labview and creat the report in excle. I create the chart into report but I can't hide the chart legend or change the font size using report generation toolkit.
    I appriciate you guys time.
    Thanks
    Solved!
    Go to Solution.

    Howdy!
    What is the version of LabVIEW and Report Generation Toolkit you are using? Have you taken a look at the LabVIEW Example Column Graph (Excel).vi
    and looked at the help for Excel Insert Graph VI and Excel Set Graph Font?
    Joshua B.
    National Instruments
    NI Services
    NI Support Resources
    NI Training Resources

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

  • Report Generation Toolkit Excel errors and Libraries, Classes

    Hello All,
    I'm using the Report Generation toolkit Excel functions to handle some data and create graphs.  I'm running into problems with the Add Worksheet.vi.  At the very start of the vi, it closes the reference to Shapes.  Occasionally, the Close Ref will throw an error.  I haven't pinned down the exact cause yet (probably an invalid reference).  The error itself wouldn't be a problem.  Under other circumstances I would choose to ignore it and continue on.  The problem is, this is stored in a Class Library controlled by NI.
    Solutions I've tried without success:
    1.) Make changes, and save the new vi with another name - can't do it because it's encapsulated and the Library is password protected.
    2.) Install toolkit in something other than the default folder, so I can make changes and put it under Source Control - installer doesn't allow a new path to be entered.
    3.) Change the vi where it is.  This works until I move the source to another computer or I update Labview.  At that point I lose all my changes.
    Maybe it's just my inexperience with Classes, but I just don't see an elegant solution to this.  Ultimately I'd like to copy the library off to somewhere else and put it under Source Control so I can make changes and additions to it (NI folks - providing a password to unlock the lib would be helpful...).  Does anyone have suggestions on how I can accomplish this?
    Thanks in Advance,
    Doug

    Hi Ben,
    Sorry about the first post.  After re-reading it, it sounds more like a frustrated rant than a request for help.
    I've attached a simplified vi to try to illustrate the problem I'm having.  I'm running Excel 2007.  Please open the vi, then open Excel Add Worksheet.vi.  At the start of the vi, Close Ref for Excel.Shapes occasionally throws an error.  So far, I have not been able to consistently reproduce the error, so I can't really troubleshoot it.  As I recall, the error code is 1045.  The error is carried through the rest of the vi, causing invalid references to be written to Excel._Worksheet and Excel.Shapes, going out to NI_report.ctl.
    So, here are the issues I'm running into (other than the error itself):
    1.)Short of closing and reopening the file, there is no way to recover from the error.  After the error, there is an invalid reference in Excel._Worksheet.  There is no vi available to regenerate references in NI_report.ctl.  I could easily write a vi to start from Excel._Application and re-read them, but because NI_report.ctl is in a Class library (controlled and passworded by NI), I can't add the vi to the library.
    2.) I found that I could ignore the error by wiring around it.  If I disconnect Error Out from Excel.Shapes Close Ref and wire Error In from Excel.Sheets.Count to the Error In of the Close Ref, everything works fine.  Under other circumstances, I'd save this with a new vi name (because functionality changed) and continue on.  But, because the vi is part of a Class library (controlled and passworded by NI), I can't do this.  I can save the vi with the modifications (because Excel Add Worksheet.vi is not passworded), but if I pass the source off to someone else, they will have to make the same changes on their installation of the NI Report Generation Toolkit.
    Again, I can't reproduce the error with any regularity.  I've run the example vi I provided a few times and everything seems to work fine.  If I come up with something, I'll repost.  If you (or anyone) has an idea of what could be failing or if they've seen the problem, I'd appreciate a comment.
    Thanks again,
    Doug
    Attachments:
    Excel Fail.vi ‏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 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/C38CE3F3054​2D65B86256F0E00740DD8
    Prashant.

  • 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

  • Report Generation Toolkit with Excel 2003 and Excel 2000

    Hello,
    I'm using the Report Generation Toolkit to generate an Excel report from an Excel template.
    The "NI_Excel.lvclass" is included in the "source" section of the application builder options.
    I create an exe file on  a PC where Excel 2003 is installed. On a Notebook, where only Excel 2000 is installed, the application crashes at the generation of the report:
    I guess the problem is the different version of Excel but I don't know. On the developer PC with Excel 2003 it works fine.
    In this document it's only talked about different Word versions.
    How can I use the Report Generation Toolkit here?
    I'm using it that way:
    Regards

    Oh, it seems that the Report Generation Toolkit "only" supports Excel XP/2003/2007.
    I think, that's the problem.

  • REPORT GENERATION TOOLKIT AND EXCEL

    i have a problem with report generation toolkit and excel
    the problem is:
    i must read & write from a excel worksheet when this is open but when i using the report generation the worksheet is open another time
    have some solution for this problem?
    sorry for my english

    You need to close Exel when before your VI is running. Excel can not have two instances running at the same time.
    Joe

  • Report Generation Toolkit 打开现有的Excel 文件

    用activeX打开excel我会,但是属性太复杂。不想用ActiveX的方式。
    我有LabVIEW Report Generation Toolkit for Microsoft Office;
    里面的例子都是生成新的excel 文件
    如果要打开现有的excel文件,然后对里面的资料进行操作,可以透过这个toolkit实现吗?

    这个论坛没有人气吗?

  • I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 profession​al. The create new report VI opens Excel but throws error (-21471672​62- from automation open VI) when I try to open MS word. please help...

    I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

    Hi Leo22,
    Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
    Jeremy L.
    National Instruments
    Jeremy L.
    National Instruments

  • Report generation Toolkit: Excel report functions error -2146827284

    Hi,
    I'm trying to create an automated report using excel functions from the report generation toolkit in labVIEW. When I run the program that generates the report first time round (the report consists of several worksheets, each worksheet is added onto the report at a diffferent state in a state machine) it always works fine and no error is generated. However, when I run the program again it will infrequently (sometimes it does, other times it will not) generate the undefined error -2146827284, this is coming from one of the excel report functions and it cannot find it on highlight execution mode.
    Does anyone know anything about this error, why it occurs, how to prevent it?
    I would appreciate any help.
    Thanks,
    Rowan

    mebels_cti wrote:
    Found something that helped; https://forums.ni.com/t5/LabVIEW/Error-code-quot-2146827284-quot-when-trying-to-open-an-Excel/m-p/20...
    Excel still open
    So I added this;
    You should use the Application Quit method instead of killing the task. I doubt this is the cause of your issue.
    Ben64

Maybe you are looking for

  • Can I daisy-chain a G-RAID Pro 2TB with a bunch of other G-RAID's?

    Hey there, I'm wondering if there would be any issues adding a G-RAID Pro into my current daisy-chained G-RAID configuration. - I've got seven 500GB G-RAID's all daisy-chained together and running into my G5. - Two of my 500GB G-RAID's are RAIDed tog

  • Problem in home selection

    Hi, I have 3 Oracle homes in my machine. While creating DSN names from Control Panel I am selecting the Oracle Driver and selecting the alias name from the avialable list but its giving the error tnsnames error. i guess there is some problem with the

  • How to take CameraLink serial port into use in VC6+MFC?

    I'm trying to use the CameraLink serial port. Developing environment is VC6 + MFC. Serial port controlling functions reside in CLSERNAT.DLL. clsernat.h is included in the project. Following code is used for accessing tjhe functions in DLL. --snip----

  • Running Multiple JVM's on same Server has OutOfMemory - PermGen Errors

    I have a scenario where I have 2 application servers. One is running one JVM and the other is running multiple JVMs. Both are configured with: -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:MaxPermSize=256m -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassU

  • Socket security issues

    Hello, I am developing an messaging application, similar to MSN or AIM. so only text messages are passed over a socket. Does anybody know of any socket security issues there are when opening a socket on a particular port in java? If so then does anyb