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

Similar Messages

RWRBE60.exe error when generating a report to a file format

Hi people,
I'm employed as a consultant by a major Petrochemical facility in South Africa.
My problem is as follows:
Our product dispatching system contains a number of reports which need to be generated to a file format (either PDF, RTF or Text).
Whenever one of the users attempts to do the above in the Reports Previewer
(by clicking on "File" -> "Generate to File" -> "Text"); the following error is displayed:
"RWRBE60.exe - Application Error. The instruction at 0x00281036 referenced memory at 0x00000000. The memory could not be read."
This error only occurs when they attempt to run a report through the Application itself.
I've recompiled and executed the same report(s) using Reports Builder 6, and it generates the file(s) with no problems whatsoever!
Only when running said reports through the Production application, does this error appear.
Your feedback will be highly appreciated!
Thanks!

This certainly looks like a bug, but you should probably check and make sure that you're on the latest patch set (or at least patch set 10 - Reports 6.0.8.19) before contacting support and pursuing further.
Hope this helps,
Danny

Facing crw32.exe error in crystal report because of page size of mainreport

I have developed a crystal with main report which includes a subreport in the details section.
Main report is for header details of invoice and subreport is for line item details.
Page design is like
report header
page header
details a- subreport
details b
pagefooter
In subreport, in details section written a logic for getting a new page after every 10 rows, and insert a new line after 10 rows.
After running the main page, if the report conation only one page more than 10 rows, it is getting crashed with crw32.exe error.
But this report is working fine if the second page contains more than 10 rows.
Could not understand the problem and need help..

Hi,
The difference I can see is the Report Header. Format the Report Header section for New Page After. This will give the first page extra space.
I normally do not recommend having a subreport in the detail section. It would be a better suggestion to have the subreport in a Group or Page section and have your subreport return 10 records at a time. The extra line would be in the main report below the subreport.
Good luck,
Brian

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

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.

Dispose Report.vi cannot release excel

HI.
This is my first time to use the sub vi to generate excel file.
I have used New report.vi and Dispose report.vi from the report generation kit but I can see from the Window Tast Manager, the excel .exe is stil running after the Dispose report.vi.As a result of that, I cannot see the excel file when my LabVIEW programme is running.
Actually is it normal for that ?
Thanks in advance.
IO

Dear Brian K,
Thanks for your reply.
Actually I have used the VIs in the toolkit to generate the excel file.
My flow is : generate new excel file>make a new name to the worksheet to A>add a title to the data in sheet A>put the data in the worksheet A>save the file>select the other worksheet>name the worksheet to B>put some data to it>save the file>create graph >put data to graph>change the graph proporties>save the file>maxmize the excel window>dispose report.
I have setted the whole programme to be continously running.
What I suppposed is the excel file will be released after the first looping,then it will active again when the flow is reach to the VI to create excel file but in the real case, it doesn't behave like that.
So I don't know whether I have got anything wrong with my flow or it's normal for that in LabVIEW.
Thanks in advance,
Io Hui

Output required in MS Excel from Reports Oracle 10g error with built in pac

Hi All,
Our requirement is to get matrix report output in MS Excel. For that i found a report online. However, im having issues with Built-in Package OLE2.obj_type.
Below is the report log file:
******* Custom: Version : UNKNOWN
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XX_MATRIX_REPORT module: XX_MATRIX_REPORT
Current system time is 10-AUG-2012 17:23:17
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
APPLLCSP Environment Variable set to :
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
Enter Password:
REP-0736: There exist uncompiled program unit(s).
REP-0736: There exist uncompiled program unit(s).
REP-1247: Report contains uncompiled PL/SQL.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1247: There exist uncompiled program unit(s).
REP-1247: Report contains uncompiled PL/SQL.
Report Builder: Release 10.1.2.3.0 - Production on Fri Aug 10 17:23:19 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Start of log messages from FND_FILE
End of log messages from FND_FILE
Program exited with status 1
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 11242010.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Output file size:
0
Finished executing request completion options.
Concurrent request completed
Current system time is 10-AUG-2012 17:23:20
Please Help!!!

After Report:
function AfterReport return boolean is
begin
RPT2XLS.release_memory;
srw.user_exit('FND SRWEXIT');
srw.message(101,'After Report');
return (TRUE);
end;
RPT2XLS package body:
PACKAGE BODY RPT2XLS IS
     TYPE ExcelCell IS RECORD(RowNo binary_integer,
                                                                 ColNo binary_integer,
                                                                 Val varchar2(2000),
                                                                 FontName varchar2(20),
                                                                 FontSize binary_integer,
                                                                 FontStyle binary_integer,
                                                                 FontColor binary_integer,
                                                                 BgrColor binary_integer,
                                                                 Format varchar2(60),
                                                                 Align xlHAlign
     TYPE ExcelCells IS TABLE OF ExcelCell;
     Cell ExcelCells := ExcelCells();
     CurrentRow binary_integer := 1;
     PROCEDURE new_line IS
     BEGIN
          CurrentRow := CurrentRow + 1;
     END;
     PROCEDURE put_cell(ColNo binary_integer, CellValue in varchar2,
                                                  FontName in varchar2 DEFAULT null,
                                                  FontSize in binary_integer DEFAULT null,
                                                  FontStyle in binary_integer DEFAULT null,
                                                  FontColor in binary_integer DEFAULT null,
                                                  BgrColor in binary_integer DEFAULT null,
                                                  Format in varchar2 DEFAULT null,
                                                  Align in xlHAlign DEFAULT null
                                                  ) IS
     BEGIN
          Cell.Extend;
          Cell(Cell.Last).RowNo := CurrentRow;
          Cell(Cell.Last).ColNo := ColNo;
          Cell(Cell.Last).Val := CellValue;
          Cell(Cell.Last).FontName := FontName;
          Cell(Cell.Last).FontSize := FontSize;
          Cell(Cell.Last).FontStyle := FontStyle;
          Cell(Cell.Last).FontColor := FontColor;
          Cell(Cell.Last).BgrColor := BgrColor;
          Cell(Cell.Last).Format := Format;
          Cell(Cell.Last).Align := Align;
     END;
PROCEDURE run IS
          Application OLE2.OBJ_TYPE;
          Workbooks OLE2.OBJ_TYPE;
          Workbook OLE2.OBJ_TYPE;
          Worksheets OLE2.OBJ_TYPE;
          Worksheet OLE2.OBJ_TYPE;
          WorkCell OLE2.OBJ_TYPE;
          WorkColumn OLE2.OBJ_TYPE;
WorkFont OLE2.OBJ_TYPE;
WorkInterior OLE2.OBJ_TYPE;
          ArgList OLE2.LIST_TYPE;
     BEGIN
          Application := OLE2.create_obj('Excel.Application');
          OLE2.set_property(Application, 'Visible', 1);
          Workbooks := OLE2.get_obj_property(Application, 'Workbooks');
Workbook := OLE2.invoke_obj(WorkBooks, 'Add');
          Worksheets := OLE2.get_obj_property(Workbook, 'Worksheets');
          Worksheet := OLE2.get_obj_property(Application, 'ActiveSheet');
          for i in Cell.First .. Cell.Last
          loop
               if Cell(i).Val is not null then
                    ArgList := OLE2.create_arglist;
                    OLE2.add_arg(ArgList, Cell(i).RowNo);
                    ole2.add_arg(ArgList, Cell(i).ColNo);
                    WorkCell := OLE2.get_obj_property(Worksheet, 'Cells', ArgList);
                    ole2.destroy_arglist(ArgList);
                    ole2.set_property(WorkCell, 'Value', Cell(i).Val);
                    ole2.set_property(WorkCell, 'NumberFormat', Cell(i).Format);
                    if Cell(i).Align is not null then
                         ole2.set_property(WorkCell, 'HorizontalAlignment', Cell(i).Align);
                    end if;
                    WorkFont := OLE2.get_obj_property(WorkCell, 'Font');
                    WorkInterior := ole2.Get_Obj_Property(WorkCell, 'Interior');
                    if Cell(i).FontName is not null then
                         OLE2.set_property(WorkFont, 'Name', Cell(i).FontName);
                    end if;
                    if Cell(i).FontSize is not null then
                         OLE2.set_property(WorkFont, 'Size', Cell(i).FontSize);
                    end if;
                    if mod(Cell(i).FontStyle, 2) = 1 then
                         OLE2.set_property(WorkFont, 'Bold', 1);
                    end if;
                    if mod(Cell(i).FontStyle, 4) > 2 then
                         OLE2.set_property(WorkFont, 'Italic', 1);
                    end if;
                    if mod(Cell(i).FontStyle, 8) > 4 then
                         OLE2.set_property(WorkFont, 'Underline', 2);
                    end if;
                    if Cell(i).FontColor is not null then
                         OLE2.set_property(WorkFont, 'ColorIndex', Cell(i).FontColor);
                    end if;
                    if Cell(i).BgrColor is not null then
                         OLE2.set_property(WorkInterior, 'ColorIndex', Cell(i).BgrColor);
                    end if;
                    OLE2.release_obj(WorkInterior);
                    OLE2.release_obj(WorkFont);
                    OLE2.release_obj(WorkCell);
               end if;
          end loop;
          ArgList := ole2.create_arglist;
          ole2.add_arg(ArgList, 'A:Z');
          WorkColumn := ole2.Get_Obj_Property(WorkSheet, 'Columns', ArgList);
          ole2.destroy_arglist(ArgList);
          ole2.invoke(WorkColumn, 'AutoFit');
          OLE2.release_obj(WorkColumn);
          OLE2.release_obj(Worksheet);
          OLE2.release_obj(Worksheets);
          OLE2.release_obj(Workbook);
          OLE2.release_obj(Workbooks);
          OLE2.release_obj(Application);
     END;
     PROCEDURE release_memory IS
     BEGIN
          Cell := ExcelCells();
          SYS.DBMS_SESSION.free_unused_user_memory;
     END;
END;
We are getting the error in log file Report contains uncompiled PL/SQL.
due to ole2.obj_type...

LV 2009 Dispose report leaves Excel in memory

Hello all,
I am hoping somebody can help, we think that the below problem is part of a larger problem where LV2009 is crashing on our server with memory is full errors.
In the attached vi which contains the excel portion of our larger vi with dummy data, it duplicates the issue where everything seems to run OK, but when you check windows task manager it appears the Excel is staying in memory after this executes. Despite the dispose report being at the end of the chain.
any help at all would be greatly appreciated.
thanks
Attachments:
test.vi ‏31 KB
test.xls ‏22 KB

See this thread.
Message Edited by PJS on 11-05-2009 12:51 PM
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?

XL Reporter Error - Error Starting Excel! Cause: (Retrieve Excel Interface)

Hi all experts,
My customer is running SAP B1 8.8 PL13, with MS Office 2003.
One of the workstation is encountering XL Reporter error when trying to generate XL Reports.
Error starting Excel! Cause: (Retrieve Excel Interface) Automation error
Library not registered.
I have tried checking the Excel Macro security setting, COM-Addins, changing Excel.exe.config file to use .NET Framework 1.1. But the error still persists.
I have also tried uninstall SAP B1 client, remove SAP folder, the reinstall B1 client again, but the error still exist.
Any other idea except reformatting PC?
Thanks,
Taw-Fey Tan

Hi Julie,
There seems to be 2 COM-Addins in Excel.
SAP Business One
SAP Business One XL Reporter
I am unable to delete the first one while keepint the second. Not sure why it keeps coming back and reappear itself.
Taw-Fey Tan

Cannot build the query or generate the report - BI4.0 Dashboard on WebService Error

Hello All,
I am trying to create a Dashboard with WebService connections in SAP BI4.0 SP04. While running the dashboard I am receiving the error, Cannot build the query or generate the report. I have already set the refresh parameter to TRUE (bound to an excel cell and I have tried with 1 also). Back end WebI Reports of the BIWS connections are created from BEx queries through BICS connection. I have two prompts to run the Web Service and the report. Please share your thoughts regarding this.
Thanks and Regards,
Debajyoti Dan

Hi All,
I have found the issue. The problem is coming only when I am receiving prompts from BEx query and trying to use them through dashboard. I replaced these BEx prompts with the same in WebI report. Then the entire functionality started working correctly from dashboard.
But, this is only a work around and can not be applied at all times. So I have raised a message for the same to SAP. I will update the thread based on what I receive from SAP Support.

Error when running a report to Excel

I receive an error when trying to run a report out of FDM in Excel. The report runs fine in PDF form but when running in excel it loses the formatting of the report and I get an error saying "excel found unreadable content". This report runs in all locations within FDM except for one. Has anyone ever come across this error? I am not sure why it would work for all other locations and just come up with an error for one location.

Did you write that software, COTS package called Medgate?
If not then ask that company for support. No one here would know how to fix it. They are using the CR RDC report engine.
Thank you
Don

Report builder error after applying sql server 2008R2 SP3 when click on report builder gives error like 'Application validation did not succeed. Unable to continue.

Hi All,
I applied SQL server 2008 R2 SP3 recently but report builder doesn't work since then
When click on report builder gives error like 'Application validation did not succeed. Unable to continue.
and when I try to see details the error summary like following:
+File, Microsfot.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
this is urgent.
Please reply me asap.
thanks a lot in advance.
Regards,
Nik
Regards, Naman

Hi nikp11,
According to your description, you recently updated SQL Server 2008 R2 to SP3, Report Builder doesn’t work since then the error occurs: "Application validation did not succeed. Unable to continue".
This is an known issue in SSRS 2008 R2 SP3 that Microsoft has published an article addressing this issue. It is not planning to release a fix for this issue. But we could implement one of the following workarounds:
Install and run Report Builder 3.0 of SQL Server 2008 R2 RTM.
Install and run Report Builder of SQL Server 2014.
Uninstall Service Pack 3 then uninstall Service Pack 2 and then reinstall Service Pack 3.
Reference:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch
Thank you for your understanding.
Best Regards,
Wendy Fu

XL Reporter error. Excel cannot start

Hi all, I have a SAP B1 client installed on a PC with Vista Business 32 bit OS and Excel 2007. The database server is windows server 2008 64bit. The B1 client works fine and XL reporter opens correctly.
When I try to generate a report in XLR it gives the error:
"Error starting Excel. Cause: (Set interface properties) Object variable or with block variable not set"
I have three identical machines, XLR works fine on two of them and not on the other.
I cant see any difference between the computers.
Does anyone have any experience with this error?
Cheers
Neil

This error is caused by using the incorrect client. You need to use PL 46 or higher for Mssql 2008
The problem is that it is not easy to see which client install pack you are installing unless it is from the CD.
I only figured this out by looking at the file creation dates in the client install. I uniinstalled the client from the vista machine and the Win 2008 64bit Dell R710 terminal server and installed the PL 47 client from a CD. It installed fine and upgraded itself and then installed the addins.
XL Reporter worked fine then.
When setting up for the first time dont forget to enable macros in the trust centre in Excel . Select Office Button>Excel Options> Trust Centre > Trust Centre Settings > Macro Settings > Enable all macros. Also trust access to the VBA Project.
Then go to Office Button > Excel Options > Add Ins. Down the bottom choose Com add ins and select go.
If SAP B One XL Reporter is not present select ADD and navigate to C:\Program Files\SAP\SAP Business One\AddOns\XLR\XLReporter\IXXLReporter.dll and OK out.
To get these Excel items to work start Excel by right clicking the Excel icon and select Run as Administrator

Dispose Report closes all Excel spreadsheets

With Report generation toolkit, I am creating an excel spreadsheet. I create a "New Report", do stuff and "Dispose Report". When I "Dispose Report", it closes ALL excel spreadsheets that are open, including ones that are not part of the LabVIEW application, with no warning. Is this correct? How do I avoid this annoying behavior?

Henry,
As Zvezdana mentioned the 1.0 version of the Report Generation Toolkit does work this way. Since that behavior isn't very desirable it has been changed in the 1.1 version of the toolkit which released in March. The new version only closes the report for the particular reference being disposed. You also have the option of not closing the report when you dispose the reference.
Kennon

User gets crw32.EXE error on some reports

I have a user who gets a crw32.exe error message when running some custom reports he has created.   The error signature is as follows:    AppName: crw32.exe;   AppVer: 11.0.0.1252; ModName: mfc71u.dll; ModVer: 7.10.3077.0;   Offset: 00ac991;
We have already uninstalled and reinstalled Crystal (Standard version). The user is set up as a local administrator.   He used to be able to perform a work-around to get the reports to run. He would first open another report and run it, and then open one of the problem reports and it would then run successfully.   This is no longer working.
Any ideas?

Additional Information:
While looking at replies to my response and doing the follow-up suggested by these replies, I discovered that if the user launches Crystal Reports first and then uses the application to open the report file, he can run the report successfully. In the limited testing, this appears to work every time!
However if he double-clicks on the report file (*.rpt) in the directory (Windows Explorer) and through the file association, Crystal launches, he will get the error on these few reports every time!   So he has a work around at least, but if you have any further suggestions, I'd love to hear them.

Build EXE error in excel dispose report

Similar Messages

Maybe you are looking for