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

Similar Messages

Word_print.vi 1015 error when running exe

I created a vi that generates report in word and prints to default printer. The vi works fine in three different computers with office 2000, 2003 & 2007. But when I create an exe, there is an error: 1015 Word_Print.vi in Print Report.vi. The error is only in system running office 2000. The application was built using LV 8.2 & office 2007. The exe is created with dynamic word vis in support files. I also tried addind Word_print.vi in the support files.
Could you please let me know what I else I could do?
Thanks
U

Ah, understood. Which version of the Report Generation Toolkit do you have installed? All versions, except maybe 1.1, have a folder on the package CD called Compatibility. Within this folder are directories such as Office 97, Office 2000, [Office XP], [Office 2003], and [Office 2007] (toolkit version determines if you have the items in brackets). If you dig into these directories, you'll eventually discover the file _wordsub.llb. This library contains the appropriate _Word Dynamic VIs.vi that you'll want to include in the "support files" section of the application builder. Refer to the Office.txt document found within C:\Program Files\National Instruments\LabVIEW 8.X\vi.lib\addons\_office directory to confirm what I said. Thus, to create an executable that will print from your Office 2000 test machine, include the _Word Dynamic VIs.vi from the Compatibility\Office 2000\vi.lib\addons\_office\_wordsub.llb library on your Report Generation Toolkit CD.
Peter K.
National Instruments

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

Add Report Generation toolkit for Microsoft Office in exe

Hi
I am having a problem. I am using LabVIEW 8.20, Report Generation Toolkit for Microsoft Office 1.1.2 and Microsoft Excel 2003. My OS is Windows XP (SP )
I want to build the vi attached below into an exe. The vis that I used are from addons>>_office>>excel.llb. I follow the suggestion found in the link below and add in all the files in excel.llb into my project so that it can be added into the executable as dynamic vis. However, some vis in excel.llb cannot be added into my project. After I have add all vis that can be added into the project, I build an application (exe) with the vi below as the Main vi and all other added vis (from excel.llb) as dynamic vis. After that, I build and run this exe on the same PC. I am unable to run it.
This vi will save datas when I click on the stop button. After I click on the stop button, a window will pop-up and prompt me to select which directory to save the vi. When I run the exe, I type in test.xls (for example) but the file saved is a picture and not an excel file. If I just run the vi instead of the exe, Excel will open and datas and graph will be displayed in Excel.
May I know where did I done wrong??
How do I use the Report Generation Toolkit in an executable with Microsoft Excel?
http://digital.ni.com/public.nsf/websearch/C38CE3F30542D65B86256F0E00740DD8?OpenDocument
Thank you & Regards
Lee
Attachments:
Self-Regulating.vi ‏132 KB
Untitled Project 1.zip ‏3841 KB

Hi centerbolt,
Thank you for your reply. I have tried adding in just that dynamic vi found in Excel Library and my main vi but it still cannot work. Is there anything that I need to look out as well?? [View attached picture.]
Thank you & Regards
Lee
Attachments:
added.JPG ‏92 KB

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

Report Generation Toolkit error when running exe not vi

Unknown System Error in Get Report Settings.vi->Get Current Font.vi->Excel Easy Table (str).vi->insert table and save file.vi->80x test suite.vi
1. The above is an error I get from my exe
2. I do not get this error when just running the vi.
3. On several report gen functions cohersion dots are on my refnum input. Is this the cause of my problem with the exe?
I guess there is an another learning curve when dealing with the app builder.
Any suggestions would be appreciated.
Thanks
Brian
CLAD
Brian

forget what i wrote. it was my vi.
funny, most of the time it aint LabVIEW causing the problem but the program itself.
Brian

Error when running EXE but not from editor. How do I find it?

When I run my app from the editor, the program works fine. But when I try to run the EXE, I get an "index out of range" error. (???)
I examined my code extensively but I can't figure out for the life of me where the error's coming from.
Any advice on how to track it down? Thanks.

Find out what is using indexes then correct whichever code is using indexes. Apparently you have not examined your code extensively enough.
Can't you see details of the error and find what line the error occured on?
La vida loca
Monkeyboy brings an interesting point.
Try wrapping all of your code in a try-catch block and msgboxing the stacktrace, that way you can find the line.
“If you want something you've never had, you need to do something you've never done.”
Don't forget to mark
helpful posts and answers
! Answer an interesting question? Write a
new article
about it! My Articles
*This post does not reflect the opinion of Microsoft, or its employees.

Webi report throwing 500 internal error when run

hi all,
when i tried to run one of my report , it is throwing 500 internal error INF; the same does not happen with ohter reports in the same folder.
can someone help on this. I am admin with full rights who is not able to perfom this.
informations:
BO XI3.1 sp3 fp 3.2
bo installed on one seperate server. and hosted on websphere.. and other web deployments made on websphere again.
rgds
shravan

this report is using merge cells and cross tabs which is a bug in the product till XIR3 SP3 FP3.2 so an upgrade to FP3.5 will fix this issue. again. this does not happen with all the reports.
this is the solution given the SAP vendor.
rgds
Shravan

Bug Report - DB toolkit returns error when calling the DefaultDatabase property with SQLite

There's an old bug in the DB toolkit where calling the DefaultDatabase property returns error -2147217887 if you're using certain DBs (such as SQLite or PostgreSQL and I believe MySQL as well).
The problem is that this property is called by a VI which is used in some of the commonly used VIs (such as the insert VI),
causing them to fail. Whoever wrote the code was aware of this issue,
since they added a comment about it, as you can see below.
The immediate fix for this is pretty easy - add code to ignore the error or don't call the property at all. It's not used anywhere in the toolkit and unless you're using the VI yourself to get the property, this won't break any code. The problem with this is that you need to do this in every PC.
NI already has a CAR for this (CAR 232063) and should hopefully fix it, so there's no need to take further action at the moment. This post is for people searching for this in the future.
Try to take over the world!

Interesting. I have seen this before but it returned a different error code. (Error -2147352567)
=====================
LabVIEW 2012

Report Generation Toolkit failure with Win 7 and Labview 2013

I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files. If I try to run the New Report.vi with report type Excel selected I get error -2146777998. Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error. Selecting Standard Report or HTML also run without errors.
I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
Solved!
Go to Solution.

I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt. The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

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

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

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

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

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

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

Report generation toolkit VI error when running EXE

Similar Messages

Maybe you are looking for