Application Build Failure on Excel.Print Report call

Developing software in LV2009 that uses Report Generation Toolkit to read/write from Excel templates. Program runs fine in development mode. AppBuilder crashes on *.exe build when adding NIReport.lvclassrint Report.vi
Digging down, I find a broken run arrow on the NI_Excel.lvclassrint Report.vi as shown here:
According to the Show Errors dialog, there is an unwired or bad terminal on the PrintOut invoke node; however I have not made any changes to this shipping VI (that I know of). I did try wiring all the unused inputs (empty strings to From, To, and PrToFileName; false booleans to Preview, PrintToFile, and Collate) after I ran into the error, but that had no luck either. Also tried inserting To Variant conversions for all input elements, just in case there was a problem in the implicit data to variant conversion.
I have also tried a ctrl+shift+run compile of the whole application, but that doesn't seem to get it to un-break, either.
Has anyone run into this problem before? It's weird that it would just break like that--I had actually compiled this particular executable before, using pretty much all the same Report Generation Toolkit VIs that I am using now. The only difference since the last build was that I replaced a Report.SaveAs function with a Report.Save function.
Also of note: I have included all the Report classes in my project and build specification in order to compile the dependencies into support libraries to minimize the number of labview files included with the executable distribution. This is probably why an error with the Print Report.vi calls is crashing the AppBuilder even when I don't explicitly call that VI anywhere in my code.
Solved!
Go to Solution.

Hey Guys,
I know this post if kind of old but I hope maybe one of you can help me out. I'm using an invoke node similar to what is above to print out an Excel spreadsheet to the default printer. My issue is that when I try to print from the spreadsheet from the executable, the executable crashes. I know it is that invoke node. The reason why I say that is because until recently I had two development computers, one running on Windows 7 LabVIEW 2010, and one running on Windows XP LabVIEW2010. The original .exe was built with the XP machine, when I tried to make some changes with the Windows 7 machine and open the project it would say that there was a missing connection to the invoke node even though I did not touch that part of the application. I would then remove the invoke node, add it again and it would clear the error for whatever reason. I would then build the .exe with the Windows 7 machine and when it would run, the application would crash at the point where it goes to print the spreadsheet. I got around this by building the .exe with the Windows XP machine, and it worked fine without any issues. However, my Windows XP machine cra**ed out so i'm no longer able to build the .exe on the XP machine . I needed to make some changes to the .exe not anything involving this section of the code and for whatever reason when the application goes to print it crashes. I get some criptic crash report from Windows that is pretty much useless. I think its a Windows thing. This was workign correctly though until I did a build on the Windows 7 machine.
Attachments:
Printout Invoke Node Excel.png ‏70 KB
crash1.png ‏22 KB
crash2.png ‏23 KB

Similar Messages

APEX 3.0 print report error (empty file).

I installed BI 10.1.3.2.0 successfully.
I tested my convert servlet (which comes with BI Publisher)
by trying to go there directly in browser:
http://roman:80/xmlpserver/convert
I get the message in Firefox:
"500 Internal Server Error
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details".
The application.log contents:
"07/04/09 16:42:38.928 xmlpserver: Servlet error
javax.servlet.ServletException: XML data or RTF template is null.
     at oracle.apps.xdo.servlet.Converter.doPost(Converter.java:99)
     at oracle.apps.xdo.servlet.Converter.doGet(Converter.java:50)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind[Oracle Containers for J2EE 10g
(10.1.3.1.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)".
It's mean that servlet is up and running.
I specify the following attributes:
Oracle BI Publisher: Advanced Support
Print Server Protocol: HTTP
Print Server Host Address: roman (the name of my computer)
Print Server Port: the port 80
Print Server Script: /xmlpserver/convert
When i click on link "Print report" in my application i receive the empty pdf file
(file size is zero).
Is it any idea ?
Regards,
Roman

Hi Marc!
I uninstalled BI EE. Then I installed Bi EE again. I selected the Basic setup and BI Publisher only. BI Publisher has been successfully installed on my computer.
The number of port is 9704. (My previous mistake was the port number - 80!!!).
Then I start oc4j.
I tried Application Builder home page built-in report. It's work fine!
But i received some problems with print report in my own application.
If i selected "Use Generic Column Names (parse query at runtime only)" in source settings of my region i received an empty PDF file (0 bytes).
When i selected "English (United-States) en-us in Globalization settings and also
selected "Use Query-Specific Column Names and Validate Query" in source settings of my region i received the fine report.
I am using the "Default report Layout".
But I want to receive the report based on "Query-Specific Column Names and Validate Query". And also I want to have "Russian (ru) Globalization settings in my application.
Do your have any advice ?
Regards,
Roman.

Report Generation for Excel does not work after using the Application Builder

I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

Hi
I usually build exe-files, which sometimes also have report functionality.
Open the Application Builder and check the following things:
1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
Hope this helps.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
report.zip ‏25 KB

MS office report not working when application is compiled (application builder)

I'm finishing up an application that includes several MS office reports (opens a MS Word template). The template is opened, the bookmarks are filled, then the file is saved (to our internal network) as a .doc file. The New Report.vi is used to open the .doc file, the Print Report.vi is used to print the file, then the SMTP send file.vi is used to email the file.
Everything has been working fine then I decided to build the application for distribution. Big mistake! An installer is made. When I install the application I get "File not found" (error 7) errors each time I attempt to run this section of code. Incidentally, This app. also uses the SQL database toolset to read and write to a database. No problems with the database.
I thought it might have something to do with the Word templates being on the network. I copied everything to my local PC and built another application. Same problems.
I suspect I'm doing something wrong in the Source Files tab of the Build Application or Shared library window.
I'd really appreciate your help.
thanks,
todd

Most likely, you're looking at a path problem to the template file from the applicaiton.
When you build a VI into an applicaiton, the path to that applicaiton changes. If originally the VI that calls the template file was located "c:\app\caller.vi", after you build the executable, that same VI will now be located at "c:\app\toplevelVI.exe\caller.vi".
The executables name will now actually be a part of the path. So you may need to add an extra "Strip Path" function somewhere to get you to the real path to the Excel file. Of course this is just a guess without seeing your code. You could try going back to the LabVIEW code and add a path indicator where you are building the path, then re-build the application and run it so you can see what the path is after it's built.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

MS Office Report problems after compliing (application builder)

I'm finishing up an application that includes several MS office reports (opens a MS Word template). The template is opened, the bookmarks are filled, then the file is saved (to our internal network) as a .doc file. The New Report.vi is used to open the .doc file, the Print Report.vi is used to print the file, then the SMTP send file.vi is used to email the file.
Everything has been working fine then I decided to build the application for distribution. Big mistake! An installer is made. When I install the application I get "File not found" (error 7) errors each time I attempt to run this section of code. Incidentally, This app. also uses the SQL database toolset to read and write to a database. No problems with the database.
I thought it might have something to do with the Word templates being on the network. I copied everything to my local PC and built another application. Same problems.
I suspect I'm doing something wrong in the Source Files tab of the Build Application or Shared library window.
I'd really appreciate your help.
thanks,
todd

Todd,
You need to add a dynamic VI to your list of Source Files in the Build Application window. The one you need is called "_Word Dynamic VIs", and it can be found at \vi.lib\addons\_office\-wordsub.llb . Doing this ensures that the executable can find the appropriate code when it is asked to dynamically load some Word-related VIs at execution-time.
I consider the difficulty of getting everything right when building executables to be just about the biggest problem that LabVIEW has, so don't feel too badly about it. I believe this requirement is covered somewhere in the Report Generation Toolkit documentation, but I think the process should be easier and more transparent to the user when they are working with NI-produced toolkits.
--John

Application Builder for labVIEW 7 Doesn't support any report generation function

I'm Using LabVIEW 7.0 to build an application My Application is exporting data to an excel report. the vis were working great until i tried to creat an .EXE file. The application is working fine but when i try to generate the report nothing happens.
So, I decided to test the report generation functions alone (New Report.vi, Append report text.vi and Dispose Report.vi). The Problem Still there, the .EXE file takes no action when i attend to generate a report. any suggetions please.

Shady Yehia wrote:
> I'm Using LabVIEW 7.0 to build an application My Application is
> exporting data to an excel report. the vis were working great until i
> tried to creat an .EXE file. The application is working fine but when
> i try to generate the report nothing happens.
>
> So, I decided to test the report generation functions alone (New
> Report.vi, Append report text.vi and Dispose Report.vi). The Problem
> Still there, the .EXE file takes no action when i attend to generate a
> report. any suggetions please.
Another possible reason besides of possible path problems: Are you
running that application on the same computer? If not you need not only
to install the Runtime-Engine (automatic when you create an installer)
but also the Report Active X support.
To include that into the installer
you go into the Installer Settings Tab, then press the Advanced button
and make sure that you check the NI Reports Support checkbox before
creating an application build.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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.

Application builder exe does not load excel

I have used application property node and invoke node to cerate a set of VIs that read and write data to an Excel sperad sheet. This works fine in when running in LabVIEW, however when I run myApp.exe as build from application builder, the data does not get logged to Excel. The file dialog appears to open the XL Spreadsheet but not data gets logged nor is any error reported?
What is going on? All the VI are in the same project folder? Is there some additional addon run-time the must be installed on the target machine? I am uisng LabVIEW 2012 on the development station with Win7 Pro and Office 2010 on both the devleopment station and the target system. Is there one document that describes using Application Builder? It was not clear that I needed both LabVIEW and VISA run-time engines to get my application.exe to run on the target. Is there something simialr I must do to get Office to work as well?

I was finally able to track this back through by starting from scratch and received an error code, which led me to this post:
https://forums.ni.com/t5/LabVIEW/Error-2147319779-Excel-ActiveX-and-Broken-LabVIEW-Icon/td-p/2354776
Deleting the "1.7" items solved the problem.

How to send the report output to the application server in a excel file

Hello,
how to send the report output to the application server in a excel file.
and the report runs in background.
Thanks in advance.
Sundeep

Dear Sundeep.
I'm providing you with the following piece of code ... Its working fine for me ... hopefully it suits your requirement ...
D A T A D E C L A R A T I O N *
TYPES: BEGIN OF TY_EXCEL,
CELL_01(80) TYPE C,
CELL_02(80) TYPE C,
CELL_03(80) TYPE C,
CELL_04(80) TYPE C,
CELL_05(80) TYPE C,
CELL_06(80) TYPE C,
CELL_07(80) TYPE C,
CELL_08(80) TYPE C,
CELL_09(80) TYPE C,
CELL_10(80) TYPE C,
END OF TY_EXCEL.
DATA: IT_EXCEL TYPE STANDARD TABLE OF TY_EXCEL,
WA_EXCEL TYPE TY_EXCEL..
E V E N T : S T A R T - O F - S E L E C T I O N *
START-OF-SELECTION.
Here you populate the Internal Table.
Display - Top of the Page.
PERFORM DISPLAY_TOP_OF_PAGE.
E V E N T : E N D - O F - S E L E C T I O N *
END-OF-SELECTION.
SET PF-STATUS 'GUI_STATUS'.
E V E N T : A T U S E R - C O M M AN D *
AT USER-COMMAND.
CASE SY-UCOMM.
WHEN 'EXPORT'.
Exporting the report data to Excel.
PERFORM EXPORT_TO_EXCEL.
ENDCASE.
*& Form DISPLAY_TOP_OF_PAGE
text
--> p1 text
<-- p2 text
FORM DISPLAY_TOP_OF_PAGE .
SKIP.
WRITE: /05(128) SY-ULINE,
/05 SY-VLINE,
06(127) 'O R I C A'
CENTERED COLOR 1,
132 SY-VLINE.
WRITE: /05(128) SY-ULINE,
/05 SY-VLINE,
06(127) 'Shift Asset Depreciation - Period/Year-wise Report.'
CENTERED COLOR 4 INTENSIFIED OFF,
132 SY-VLINE.
WRITE: /05(128) SY-ULINE.
E X C E L O P E R A T I O N
CLEAR: IT_EXCEL[],
WA_EXCEL.
PERFORM APPEND_BLANK_LINE USING 1.
WA_EXCEL-cell_02 = ' XYZ Ltd. '.
APPEND WA_EXCEL TO IT_EXCEL.
CLEAR: WA_EXCEL.
WA_EXCEL-cell_02 = 'Shift Asset Depreciation - Period/Year-wise Report.'.
APPEND WA_EXCEL TO IT_EXCEL.
PERFORM APPEND_BLANK_LINE USING 1.
ENDFORM. " DISPLAY_TOP_OF_PAGE
*& Form APPEND_BLANK_LINE
text
-->P_1 text
FORM APPEND_BLANK_LINE USING P_LINE TYPE I.
DO P_LINE TIMES.
CLEAR: WA_EXCEL.
APPEND WA_EXCEL TO IT_EXCEL.
enddo.
ENDFORM.
*& Form EXPORT_TO_EXCEL
text
--> p1 text
<-- p2 text
FORM EXPORT_TO_EXCEL .
DATA: L_FILE_NAME(60) TYPE C.
Create a file name
CONCATENATE 'C:\' 'Shift_Depn_' SY-DATUM6(2) '.' SY-DATUM4(2)
'.' SY-DATUM+0(4) INTO L_FILE_NAME.
Pass the internal table (it_excel which is already populated )
to the function module for excel download.
CALL FUNCTION 'WS_EXCEL'
exporting
filename = L_FILE_NAME
tables
data = IT_EXCEL
exceptions
unknown_error = 1
others = 2.
if sy-subrc <> 0.
message e001(ymm) with 'Error in exporting to Excel.'.
endif.
ENDFORM. " EXPORT_TO_EXCEL
*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When you click the button - Export to Excel ( GUI-Status) you'll be able to export the content of the Internal Table to an Excel file .......
Regards,
Abir
Don't forget to award Points *

How to call Graphic builder's Graph in 9i Reports

Hi everybody,
I have a graph in graphic builder.I want to print this graph on report.
I need your help please.
Asif

Hello,
In http://www.oracle.com/technology/products/reports/htdocs/faq/graph_faq_with_style.html#q102
Can I still run my existing Oracle Reports Developer 6i reports containing Oracle Graphics charts in Oracle Reports?
As noted in the Oracle Reports Statement of Direction, Oracle Graphics is no longer shipped with Oracle Reports. However, as part of the migration path, you can still run Oracle Graphics charts in Oracle Reports if you install the Oracle Graphics 6i engine in a separate Oracle Home. You should only maintain Oracle Graphics 6i as a temporary measure while you redesign your charts using the new Graph Wizard. For further details on how to configure Oracle to use Oracle Graphics 6i, please see the Graphics Migration section in the Oracle9i Application Server Migration from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2) manual.
Regards

Error 97 when running built application and printing report.

I get the following message:
Error 97 occurred at Unknown System Error in Print Report.vi->PM Workorder.vi->NEW PM main.vi
Null Refnum was passed in as input
when I try to run my built application, but it will run fine as a vi. I am using the Report Generation Toolkit with the Excel functions. I am opening an Excel template, adding data, and then printing. When I run the built application it looks like Excel is not opening up, but when I run the vi, I can see excel open and the report is sent out to the printer. I am running both the built application and the vi on the same computer.

Hello,
I found a similar problem some month ago. I solved including in the application the excel vi's library, that you will find in the labview directory addons.
I hope this info will help you!
Regards
Neon

Issue is TEXT_IO application API is not working in report builder 10g.

Issue is TEXT_IO application API is not working in report builder 10g.
TEXT_IO application api is working in report builder 6i. (Not working in upgrade from Oracle EBiz 11i to Oracle Ebiz R12)
I saw that details in some forums, client_text_io is available for form builder 10g.
Is any other api available for report builder 10g?
If it is available what steps we need to do?

All the CLIENT_% procedures are part of webutil in Forms. Forms uses the Java applet on the client PC to perform actions on the local PC via webutil. This is not possible for Reports.
You can still use text_io on the server, but you need some other way to copy the files to/from the client PC.
I wonder how you used the functionality in EBS R11. Even R11 uses web reports, so text_io already worked on the server, not the client PC.

Passing arrays with Call Library Function does not work after application builder

Calling a DLL with Call Library Function which requires an array of data works correctly in Labview, but after building an exe with application builder, the call no longer works. Dereferecing the pointer in the DLL retuns all 0s and not the actual values.
Solved!
Go to Solution.
Attachments:
TEST.zip ‏28 KB

I did not run your code because it is a little unclear to me what it does.
Two things:
First, is the DLL you are calling the DLL-ified version of PopUpNames.vi? Then the problem is likely that the panel is not being built into the DLL.
When LabView builds an application / dll, it strips the front panel and block diagram from all VIs that it doesn't think need to show a panel at run time. This reduces file size and increases code security. The App Builder's panel inclusion logic can be overridden by Build Specifications -> Source File Settings -> Remove front panel. A better method is to put a property node on a control in a window you want to show marking it "visible"; this is sufficient to tell the App Builder it should keep the panel.
Currently Source File Settings shows "no dependencies" (clearly incorrect---another evil side effect of Express VIs I guess) but if you change the settings as shown below to keep ALL panels, one might hope the App Builder can figure it to keep the panel when it deconstructs the Express VI. (Alternatively convert the Express VI into a regular one.)
A second comment: I am a bit flummoxed at the larger goal here. You are calling LabView DLL from LabView, which doesn't make a lot of sense, so I assume your larger goal is to call LabView from C or vice-versa. In that case be aware that your DLL is x86 (32-bit) but you are passing 64-bit ints as your pointers. In this case it is 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers calling 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers, so it all works, but if your going to call this from C or whatnot you're going to have to follow that same design.
When calling C code the LabView Call Library Function does have a "unsigned pointer-sized integer" data type that always appears to be 64 bits in the dev env but which actually passes a 64 or 32-bit int to the DLL depending on the environment. The "pointer sized int" has to be 64 bits in the "LabView" part of the code because LabView's strong typing requires the data type to be determined at compile time. Casting all pointers to the largest data type in LabView makes it possible to write platform-independent code, but down at the Call Library level you still have to put the right number of bytes on the stack.

Build EXE error in excel dispose report

I have seen much discussion about path-relative-to-current vi problems when building EXE apps.
I am compiling an EXE which happens largely successfully, but when it encounters the Excel Dispose Report vi at the end of my Excel report creation section, it stops with 'error 7 at open vi reference in Dispose report ...excel quit vi ... file not found'. It works without a problem in the un-compiled version. I am just using the standard Excel Dispose Report vi out of the report generation library.
Can anyone enlighten me about how to clear this problem?
Fred

Fred,
Did you include the dynamic VIs? See: http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8
More confirmation it is dynamic VI issue: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

Exporting Crystal Report data to the Excel Print Headers

Hello everyone. I am trying to do something with Excel headers that is a little more advanced than the usual. I have multiple reports that are designed to export to Excel. Normally I only export a report header. However, I have a customer who wants a label to appear in each page header and footer in Excel. Here is the catch - they want the label to appear in the Excel print header and footer, not just on the main excel page. The label contains an SBU marking, so there is a requirement that it gets printed on every page.
If you are not familiar with the print header, it is a separate section of an Excel document that appears when you print the excel document. For this operation, I don't think I can use the built-in Crystal Export options. I have tried to Export to Microsoft Excel and I can send the page header and footer to the Excel data sheet, but not to the print header/footer.
Thanks for your help!
- David

Hi David,
I haven't worked with Excel's headers and footers but you are correct that Crystal can't export to those sections. I have though had to make modifications to an Excel file after exporting and I believe you will need to do something similar to what I did.
After I exported the report to Excel, I had a program I wrote that opened the Excel file and modified it. In my case I just had to encrypt it, zip it up and email it. You may need to do something as well outside of Crystal and Excel. Crystal doesn't export to an Excel template so automating it in Excel wouldn't work.
Good luck,
Brian

Application Build Failure on Excel.Print Report call

Similar Messages

Maybe you are looking for