Failure Report Generation

Dear All,
There is a sales process chain that runs daily that is scheduled to pull data from Oracle directly to BW. Due to wrong Billing document the pull fails at times. How is it possible to generate a mail or a failure report of data pull activity and send it to concerned party when the process chain fails? I have heard of a certain IT mail. Kindly share any info or docs on possible solution.
Regards,
Ratish
[email protected]

Hi,
Right click on the process for which u want to send message and in the context message u will have option to CREATE MESSAGE click on that then you will get option Messages for FAILURE , SUCCESS and both , then select which option need crete variantant and you will get the maintain Recipient list.
Thanks
Krishna Reddy.

Similar Messages

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.

Report Generation Toolkit, Print Excel Report, LabVIEW Crash

Hello,
when printing a report generated with the report generation toolkit for excel my build application crashes on our customers PC.
When I run this application on my PC it works fine.
The problem is the active X invoke node that trys to print the report but i cant get any error messages to find out where to locate the problem.
Maybe that there is a problem with the active X node or the Excel Version on the customers PC?
I use LabVIEW 2010 and Excel 2007 the customer has Excel 2003 SP 3.
I changed the report to generate it in Word where the Print_Report.vi fine on both PCs. But in Word Report there is called another active X invoke node to print the Report. So it seems for me that there really is a problem with the Print in Excel active X invoke node.
Mybe someon can help me in finding out whats the problem.
Greetings Daniel.
Solved!
Go to Solution.

Hi Daniel,
your behavior has been reported by others. For example:
Application Build Failure on Excel.Print Report call
http://forums.ni.com/t5/LabVIEW/Application-Build-Failure-on-Excel-Print-Report-call/m-p/1563242
Problem posted: 05-17-2011 02:19 PM
Workaround posted: 06-01-2011 and later
So their workaround was to use Excel 2007 or 2010 instead of 2003. Is this working for your customer?
Best Regards,
Jan

Report Generation Toolkit Evaluation doesn't work

Hello,
I tried to insert data into an Excel file but it seems the Report Generation Toolkit Evaluation doesn't work.
Attached file my VI.
LV is saying i have to activate the product in order to run it. An error occurs on each Report Generation subVI, which involve i never could test my application.
I went on Help/Activate Labview component and the evalution is well activate.
Someone has an idea why the evaluation version doesn't run Report Generation Toolkit ? A solution asap please...
PS : I still have 15 days evaluation left.
Solved!
Go to Solution.
Attachments:
Test_insert_data.vi ‏9 KB
Test.xls ‏14 KB

UP
With message failure
Attachments:
Sans titre.JPG ‏50 KB

Report Generation with Endeca

Hi ,
We are trying to implement the Endeca Logging and Report Generation in our application. I have followed LogServerReportGen.pdf provided by Endeca.
1. We implemented logging API calls in our code.
2. Created a logserver component in Workbench and specified all the neccessary details
3. Created a report generation componentin Workbech
When i am trying to start the Report Generation component its failing, i am not able to figure out what is the problem here.
Aslo do we need to develop and new script and provision it in workbech for Generating report ? How this report generation works.
Can some one list out what i am missing ?
Thanks
DEV

Hi Praving,
I tried to run it from scripts tab in Workbench admin console. It ran fine without any failures
What i am seeing in the view reports tab is empty all 0 values.... but we could see lot of our call recorded in Logserver output files... somewhere the connection between them is missing. I just used the existing logserver and report generation scripts provided OOB from Endeca.
I havenet logged the key SESSION_ID in loggin calls, will it matter, do you see this as the reasong.
The below is the logserver output I could see
H2012_12_17.10_02_27{version=3.5}
L2012_12_17.10_14_10{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=210,NUMREFINEMENTS=1,NUM_RECORDS=29,PAGE_TIME=0,TYPE=UNKNOWN}
L2012_12_17.10_14_29{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=260,NUMREFINEMENTS=1,NUM_RECORDS=11,PAGE_TIME=10,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Cakes,TYPE=S}
L2012_12_17.10_14_45{AUTOCORRECT_TO=cakes,DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=100,NUMREFINEMENTS=1,NUM_RECORDS=11,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Cakys,TYPE=S}
L2012_12_17.10_15_04{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=70,NUMREFINEMENTS=1,NUM_RECORDS=4,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Wine,TYPE=S}
L2012_12_17.10_15_22{DIMS=Wine%2CBy Fulfilment Type,DVALS=/Wine/Wine%2C/By Fulfilment Type/Both,ENE_TIME=40,NUMREFINEMENTS=2,NUM_RECORDS=4,PAGE_TIME=0,TYPE=SN}
L2012_12_17.10_15_49{DIMS=Wine%2CBy Fulfilment Type,DVALS=/Wine/Red%2C/By Fulfilment Type/Both,ENE_TIME=40,NUMREFINEMENTS=2,NUM_RECORDS=4,PAGE_TIME=0,TYPE=SN}
L2012_12_17.10_16_53{DIMS=Wine%2CBy Fulfilment Type,DVALS=/Wine/Red%2C/By Fulfilment Type/Both,ENE_TIME=130,NUMREFINEMENTS=2,NUM_RECORDS=0,PAGE_TIME=0,TYPE=SN}
L2012_12_17.10_17_06{DIMS=Wine%2CBy Fulfilment Type,DVALS=/Wine/Red%2C/By Fulfilment Type/Both,ENE_TIME=110,NUMREFINEMENTS=2,NUM_RECORDS=0,PAGE_TIME=0,TYPE=SN}
L2012_12_17.10_17_20{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=80,NUMREFINEMENTS=1,NUM_RECORDS=0,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Strawberry,TYPE=S}
L2012_12_17.10_17_31{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=160,NUMREFINEMENTS=1,NUM_RECORDS=0,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Lemon,TYPE=S}
L2012_12_17.10_17_42{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=81,NUMREFINEMENTS=1,NUM_RECORDS=9,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Red,TYPE=S}
L2012_12_17.10_18_00{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=80,NUMREFINEMENTS=1,NUM_RECORDS=2,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Occasion,TYPE=S}
L2012_12_17.10_18_14{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=110,NUMREFINEMENTS=1,NUM_RECORDS=1,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Basket,TYPE=S}
L2012_12_17.10_18_31{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=140,NUMREFINEMENTS=1,NUM_RECORDS=3,PAGE_TIME=1,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Blooms,TYPE=S}
L2012_12_17.10_19_51{DIMS=By Fulfilment Type,DVALS=/By Fulfilment Type/Both,ENE_TIME=30,NUMREFINEMENTS=1,NUM_RECORDS=3,PAGE_TIME=0,SEARCH_KEY=all,SEARCH_MODE=mode+matchany,SEARCH_TERMS=Blooms,TYPE=S}

XML Report Generation in TestStand 4.1.1

I'm a fairly new user with TestStand, though I've been working with Labview for a few years now. I've written a test sequence that will be replacing a previous implementation that was done in VisualBasic.
The problem I'm running into now, though, is in the test reporting. I want to use the XML format for the reports, but I cannot seem to figure out how to customize what data is printed. I want to print the failures, and then there are some global variables that I would like to see printed in the header. I've seen the XML tutorial for TestStand 4.2, but that doesn't work for 4.1. Is there anything similar for 4.1?
Can anyone provide any resources for how to go about customizing the XML stylesheet for the report generation in 4.1?
Thanks!

Hey ADahl,
NI doesn't really support customizing style sheets. There is a great tutorial here: http://www.w3schools.com/xsl/default.asp
It's really not that hard to figure out what to change once you get digging through the style sheets. I found this site helpful when I customized mine: http://zone.ni.com/reference/en-XX/help/370052H-01/tssuppref/infotopics/report_stylesheets_details/
It lays out the sections so you can read the stylesheet better.
Failures should automatically be included in the report if that step is set to include results. Here is a doc on including other data in a report: http://zone.ni.com/devzone/cda/tut/p/id/8289 You should get your globals into the report by using one of the methods in there.
Honestly though when it comes to customizing the style sheet... there are a million and 1 ways to go about it. What I did was comb through the xsl file until I found the header information. Then I just added my own stuff in there and kind of copied off the format they had for the other stuff. Now it's looking great. I had to tweak some things here and there to get it exactly right.
Let me know if you have any other questions,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Open vi error for report generation toolkt

Originally it works fine.
Now I upgrade to win7, LV9 and office2010.
To open the old program by 8.6.1, I reinstalled LV 8.6.1 and report generation toolkit.
But still got the error as attached.
Any suggestion, thanks.
Attachments:
ss.png ‏184 KB

1. MS Office 2010 is not yet supported, since it's still just a beta. I believe there are couple of changes that Microsoft make, and it could cause a problem.
2. LabVIEW 8.6.1, and all its toolkit is not supported on Windows 7. This could cause a problkem also.
In conclusion, you should use LabVIEW 2009, Report Generation Toolkit 2009, Windows 7, and downgrade office to XP, 2003 or 2007.
More information: http://digital.ni.com/public.nsf/allkb/C9408B9F08D711E786256F3300701D01

Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

Hi all,
I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
I have made some steps, like "Open Workbook", "Write Data", etc.
My steps run well, excepts one step : "Close Workbook".
If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
I feel that I'm trying to use a reference which has been killed in the "Stop" step...
I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
Thanks,
Callahan

Hi Callahan,
SignalExpress (SE for short) does the following on the Stop event:
1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
3. The VI is then run, with those values and states.
4. SE checks to see if any errors where returned.
5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
Hope that helps. Feel free to post your LLB if it doesn't.
Phil

Report Generation: New Report.vi

Running applicaion in development mode works fine.
After compiling however I get Error 7: Open VI Reference in New Report.vi
Why am I getting this error?

Has the version of Office on your machine changed since you installed the Report Generation Toolkit? The VIs will become broken if the ActiveX interface changes, and this can happen when the Office version changes. I recommend uninstalling and reinstalling the toolkit. Also, what version of Report Generation Toolkit are you using? The latest version is 1.1.1.
-D
P.S. - I'm going to respond to your other thread that you started with a link to this one. Instead of creating multiple messages on the same question, just wait for a response to your initial thread.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Report Generation Toolkit Error (undefined erro)

Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).
Any ideas?
nrp
CLA

nrp wrote:
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.
Was it the first time you attempted to write the table to that spreadsheet?
Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.
What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...
- Partha
LabVIEW - Wires that catch bugs!

Report Generation Exe Error

Hello,
I am using LV 8.6.1 with the 1.13 report generation toolkit and I am having problems getting my built exe to work. I am trying to open an excel template and populate it with new data. I have broke the vi down to just opening excel - opening the template and then fill in some data. But at this point excel does not open at all. And naturally everything works fine in the development environment.
Error Code: -2147352573
Member not found in NI_ReportgenerationToolkit.lvlib:
Excel_open_workbook.vi
NI_Excel.lvclass: new reportsubvi.vi
I read a few help pages that said to add \vi.lib\utility\NIreport.llb and LVclass directories to the project folder and add them to the always include section of the build. But no luck so far.
Side question: The machine I want to use this on has 8.6.1 Full which does not have the extra excel functions that my developer has. Is there a way to install the DEV report generation toolkit in the full version? Then I would not need to build an exe.
UPDATE: I just tried the exe on a different machine that has a developer suite installed and it worked fine. So I guess I need to find out what else I need to add to the build to make it work.
Message Edited by _Bryan on 06-16-2010 11:58 AM
Solved!
Go to Solution.

There should be some info on this in the KB.
But first you should make sure that your version of the report generation toolkit actually supports excel 2000 (which is 10 years old)
That should be in the release notes of the toolkit
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Report-generation vi problem

On a Windows XP system using the "Text Report Example" vi, the (read) report property node item "TextFont" (stdole.Font) at the beginning of the "Font Style" vi which is a part of the "Set Report Font" vi is returning this error:
"-1073741819 Unknown System Error in Font Style.vi->Set Report Font.vi->Easy Text Report.vi"
Any suggestions as to a cause and cure?

This Knowledge Base from NI's website actually deals with this problem. The fix depends upon whether or not you have the Report Generation Toolkit for LabVIEW. There are fixes for whether or not you have the Toolkit. Hope this helps.
J.R. Allen

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

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 for FPGA VI

Hello..
I want to include the number of resources used by FPGA (LUTs, slices, blockrams etc) in my report generation.
After compilation is completed, a window showing these resources will occur. But, how can I add this compilation report in my report generation...
Please let me know..
Thanks
Prashanth
Solved!
Go to Solution.

Hi
I made a small code which helps you achieve this functionality.
Hope it helps!
In this code: I read from "toplevel_gen_xst.log" file generated for the project; search for the string "Device utilization summary" and extract the part of interest Now you add this extract to your report compiled using report generation toolkit.
regards,
Ravi.
Attachments:
image.jpg ‏60 KB
FPGA Utilization.vi ‏10 KB

Failure Report Generation

Similar Messages

Maybe you are looking for