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

Similar Messages

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

File Dialog and Report Generation Toolkit

Hi,
I designed a VI for an electrometer calibration and it works quite well The only problem I have is the following:
I used the Report Generation Toolkit to put the measurement data in an Excel file. When I run the VI I'd like a window to pop up to define the location and name of the Excel report file. If these two things are done LabVIEW should create the specified Excel file and run the rest of the code.
So i tried this with the "File Dialog" Vi and all the needed low-level File I/O VIs and it worked.
But when i connect the "File Dialog" VI with the "New Report" VI of the Report Generation Toolkit I get an error message.
Is there any solution to get this file dialog pop up window with the Report Generation VIs?
thx for any help...!
Message Edited by Flea on 12-15-2005 03:58 AM

Wow, thanks for your fast and very helpful reply devchander!
I already tried this and it works fine
thx!

ORA-20001 error when creating Tabular Form or Form and Report

Whenever I try and add a Tabular Form or Form and Report to my application i am getting the following error at the end of the Wizard.
ORA-20001: Unable to create updateable report. ORA-20001: Error creating shortcut id="" ORA-00001: unique constraint (APEX_030200.WWV_FLOW_SHORTCUT_IDX1) violatedIt's not a problem I have seen when building other apps and clearly I have managed to corrupt this application somehow.
I have loaded the problem onto apex.oracle.com for those that have access. The application number is 20325.
Any help would be very much appreciated.
Cheers Shunt

Thanks! Never thought of that.
--Andy

Build usuccessful in LV8.0.1 and Report generation toolkit 1.1.1

I am trying to build an executable. I had included _wordsub.llb and _exclsub.llb as dynamic VIs.
This message is all what I get and no executable is created.
The file already exists in the destination.
C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\addons\_office\_wordsub.llb
Any ideas?
Scientia est potentia!

This appears to be a duplicate post. Check out my response to the other thread here.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

LabVIEW 8.6 and report generation toolkit

I was wanting to upgrade to 8.6 but noticed that my rep gen toolkit(1.1.1) is not compatible.
Will NI be offering a free upgrade? or do I have to go to management and ask to purchase rep gen toolkit 1.1.3 for 500 US dollars? Purchasing the same toolkit every few years when you have an SSP for a full development system is getting kind of old.
Brian

Unfortunately there is some delay in us Aussies getting the original DVDs sent to us, so at this stage my NI rep has burned me a copy of the main LabVIEW install but I can't find the Report Toolkit on it.
I am an SSP customer but when I go to the Services Resource Centre I get this message:
Important Message
Access to the Services Resource Center could not be verified.
The email address is not subscribed and/or activated with the appropriate level of service. If this is the incorrect email address, please login here
Please confirm that your correct country information is specified, please select here
If you have just subscribed you may need to wait up to 48 hours for your subscription to be processed
If access is urgent, or to subscribe, please contact a NI Representative at (800) 206-2179. Outside of the US and Canada please contact your local NI branch office

File name collision during build that includes Report Generation toolkit. How to correct?

When I switched to LV 8.6 (it's also in 8.6.1) I started getting a file name collision warning when building an installer that included the Report Generation toolkit. The executable works, but I don't like to leave warnings uninvestigated. I don't understand 1) why it's happening now and 2) what it's recommending for the fix. Here's part of the actual warning it gives.
LabVIEW prevented a file name collision during the
build. Duplicate file names cannot be copied to the same destination. You can
rename files as part of the build process to avoid name conflicts.
The following files were moved to a unique
location:
C:\Program Files\National Instruments\LabVIEW
8.6\vi.lib\Utility\NIReport.llb\Append Control Image to Report.vi
C:\Program
Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append
Control Image to Report.vi
C:\Program Files\National Instruments\LabVIEW
8.6\vi.lib\Utility\NIReport.llb\Append File to Report.vi
C:\Program
Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append
File to Report.vi
C:\Program Files\National Instruments\LabVIEW
8.6\vi.lib\Utility\NIReport.llb\Append Horizontal Line to Report.vi...........

Hi GS,
The architecture of the Report Generation Toolkit was changed in LabVIEW 8.6 to utilize LabVIEW Classes. As such, there are some warnings during an EXE build because the class VIs have identical names. Classes were not used in the toolkit in LabVIEW 8.5 and previous...that's why you didn't see any warnings during the build until now.
Your EXE should still function properly, and you shouldn't have to change anything about your build. The purpose of the warnings is to let you know that the duplicate-named VIs needed to be handled differently during the build.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

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

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.

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

Difference between diadem and LabVIEW Report Generation Toolkit

I want to expand LabVIEW's reporting capabilities. Can someone tell me what the difference is between DIAdem and the LabVIEW Report Generation Toolkit for Microsoft Office.

Hello Mr Bean,
There are several major differences between the two solutions. I'll try and outline them as good as I can ...
The biggest different is that LabVIEW and its toolkits are programming tools and DIAdem is a ready to run application.
The LabVIEW Report Generation Toolkit basically provides an extensive library of VIs that allow you to connect LabVIEW to the MS Office library and create and edit reports in Word and Excel.
DIAdem is a stand alone application that was designed to post-process data from various sources. The tools included in DIAdem are:
1. NAVIGATOR: Allows you to import data from files (ASCII, binary, Excel, etc.) as well as DataBases (SQL/ODBC, Citadel, ASAM, etc.). The unique DataPlugin technology available within DIAdem allows you to import vitually and data file by creating a DataPlugin that describes the data format and gets linked to DIAdem. More information at: http://www.ni.com/diadem/dataplugins.htm
2. VIEW: Graphical and Numerical data inspection tool. Use cursors to zoom and scroll through your data, edit your data graphically and numerically and compare different tests.
3. ANALYSIS: DIAdem has a wide range of analysis functions, ranging from simple functions like integration and differentiation to FFTs, Order analysis and 3D data analysis.
4. REPORT: The DIAdem REPORT tool allows you to create reusable report layouts that can contain multiple axis systems (2D, 3D and polar plots) as well as tables (2D and 3D) and variables. The REPORT tool generates templates that can be usedwith multiple data sets due to the inclusion of automatic (or manula if required) scaling as well as extensive use of variables for annotations. Finished reports can be exported to printers, graphics files, the Windows Clipboard, HTML pages and PDF files (PDF writing is build into DIAdem, no extra software required). Using Scripts, it is also possible to create Word, Excel or Powerpoint reports from DIAdem automatically.
5. SCRIPT: The DIAdem scripting tools allows users to record macros or write scripts that automate complete sequences, for the import of data, via extensive analysis, to creating a publication ready report. Scripts can make reports "intelligent" by modifying the appearance of a report based on the data or calculation results that are going to be displayed in the report.
I recommend you check out the following link for more information: http://www.ni.com/diadem/
DIAdem is an extremly powerful tool for report generation. I am leaving to go on a business trip to Asia, but I would be more than happy to give you an Web presentation on DIAdem after I have returned. We could use your data and create a DIAdem report Script together online. My Email address is [email protected] and I will be back the week of Thanksgiving.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

Problem with report generation toolkit when installed new office 2010

Dear all, I had LabView 8.6.1 and report generation toolkit for MSoffice 2003 perfectly working in my laptop.
Now I have added MSoffice 2010 and report generation toolkit does not work anymore since it is linked to new office.
How can I inform Labview to link report generation toolkit to the old MSoffice 2003?
regards
Max

The Report Generation Toolkit is ActiveX based. When you install the newest version of Office it registers the ActiveX server for that software, which the toolkit adapts to and uses.
Uninstalling Office 2010 would solve the issue, otherwise you will need to look at unregistering the 2010 component of Office ActiveX - but I'm not sure if that's possible.
Regards,
Peter D

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Error When building ess/tra/tre and ess/tra/tre/trs DC's

I had customized the ess/tra/tre and ess/tra/tre/trs DC's and had them working, but I do not know what I did or what happened that am now getting the following errors when building, can anyone help tell what the problem could be?
Error
-     The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel. Fix the classpath then try rebuilding this project.
-     HDI_HNS15.02_Desstratresap.com
Error
-     This compilation unit indirectly references the missing type com.sap.xss.tra.model.openccmodel.OVSOpenCostcenterModel (typically some required class file is referencing a type outside the classpath)
-      InternalVcTreReview.java
-      HDI_HNS15.02_Desstratresap.com/gen_wdp/packages/com/sap/xss/tra/tre/vc/review/wdp
-     line 0

For anyone who might need to know, I managed to fix this by adding tra to the required projects on the build path. On the Navigator View, right click -> Properties -> Java Build Path -> Projects tab -> check dependant project.

Application doesn't work after build (database toolkit and report gen toolkit).

I wrote an application using database toolkit and report gen toolkit to retrieve some data from a database, put into a Word doc, save the Word doc and print it. It works fine when I run the vi, but when I build and run it, it does nothing. I have tried all of the settings in Projec Manager that I think might help but it still won't work right. Labview 8.2.1, XP.
Thanks,
Charlie
Solved!
Go to Solution.

Thanks for the help. I finally abondened the Word append table and used the regular report gen append table and got it to work fine. The error was 214682314. That led me to the thread about column numbers must vbe between 1 and 63, but like I said, my coulumn number is 7 so don't know what is going on. Anyway I got the vi to work and do what I want so I guess now the problem is solved (moot).
Charlie

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

Similar Messages

Maybe you are looking for