Error in Append Image to Report.vi

I wrote a VI that use "Append Image to Report.vi" provided with Labview 6.1. Inside the "Append Image to Report.vi" an error occurs after the Invoke Node of the method AppendPictureFromFile. The error code is: 2147352567 Unable to load picture.. in Append Image to Report.vi ...
Please, could you help me?
Giuseppe

Hi,
I don't know if this is the problem, but anyway...
If you build an executable, there has to be a sub directory in the main
directory of the application called "data". In the directory, there has to
be a copy of the "_exclsub.llb" library. The VI's in it are called
dynamically, and are searched for in the data directory.
Regards,
Wiebe.
"KH-Simon" wrote in message
news:50650000000500000085DA0000-1042324653000@exchange.ni.com...
> Hello Giuseppe,
>
> I have the same problem with LV 6.0.2 and Win-NT on the target
> machine. If I start the program in development mode, there are no
> problems. Do you use Win-NT? If you found a solution, let me know it.

Similar Messages

Add Image to Report Table

Hello,
In my programm i create a word report. In this report exists a table with several parameters. Now I want to add a small Image in each cell, behind the parameters, in the table. How can I add images to a table? I use the Office Report Toolkit.
Thanks
MZ

Hello,
if you search on the Office report toolkit, I think that you'll find the vi "append image to report.vi".
Software developer
www.mcm-electronics.com
PS: Don't forget to rate a good anwser ; )
Currently using Labview 2011
PORTUGAL

Append front panel image to report

I am using Labview V6.1 on a Win2000 PC 2.4 Ghz, 512MB RAM.
I am trying to use the append front panel image to report VI to append a VI panel image to a report. I am using notifiers to synch the execution of the VI with the desired front panel an the report generation process. I keep getting an error fron the Append VI that is a 1004 which is VI not in memory. How do I keep a vi in memory? I thought it would stay in memory as it is waiting for a notification from my report section for completion before closing. The notification stuff seems to work properly. Any ideas?

Here is a VI that demonstrates the problem I am having. The other VI is the VI I am trying to append to the report.
Let me know your thoughts. I will be away from this forum starting 8-27 til 9-1.
Let me know your thoughts.
put these files in a c:\P368 folder. or edit my VIs
Attachments:
testing.vi ‏81 KB
build_site_data_str.vi ‏45 KB

Append Control Image to Report stops Source Distribution from working

I have a top level built executeable that calls various external vi's using the "Call by Reference Node" function. This seems to work ok, to a point. An additional point here is this is code that I had running well in LV8.2 and am now trying to get running in LV2010 as there have been some significant changes in LV that have impacted on this project and this has forced me to change things.
The external vi that is called is stored in a "Source Distribution" directory structure, which has been generated via its own project specifications. An examination of the directories and vi's stored at the destination looks like everything should be there.
When it comes to running the vi in the source distribution directory (from the top level built executeable) I get the following error message "Error 1003 occurred at Open VI Reference in Run HTML Report Generation VI LV10.vi->Generate Reports.vi", with the additional suggestion " The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.". So it looks like there is something missing in the "Source Distribution" directories.
Doing as suggested, opening the vi in the "Source Distribution" with the development environment, shows that it has no broken arrow. My suspicion is the development environment is supplying whatever it is missing.
Using the built top level application, using trial and error and using the diagram disable structure, I have narrowed down the location of the problem to an "Append Control Image to Report" sub vi (its from the NI Report menus). Disabling this vi at the level it is called, allows the "Source Distribution" vi to run.  "Append Control Image to Report" is part of a class structure and I must say I have not used class structures so my understanding of their implications is very limited.
If I instead dive into "Append Control Image to Report" vi and disable the vast majority of its diagram (everything in the "No Error" case), the original error pops up again. Bit strange considering there are only controls and indicators and a case statement left.
I would appreciate any suggestions, as this has got me stumped. Hopefully I have made myself clear enough as it is all a bit complicated. Let me know if I haven't. Thanks.
Herbert Niesler

    Hi Caleb,
      "When the VI displays the broken arrow and displays that error in the dialog, does it take you to a particular diagram component? Does the diagram have any broken arrows or something?"...      it doesn't take me to a particular diagram. Is this possible in the RTE? If it is how do I enable it?
   I can follow the chain of broken arrows (front panel only) down to my vi that calls the NIreport vi that is causing the problem. However I am unable to open the NIreport vi's in the RTE, so cannot chase this any further down the call chain.
I have tried opening the offending top level vi (on a network drive) and it opens ok. When I close it, it wants to save some changes which i think might point at where the problem is. The attached file shows the screen shots of the "Explain Changes" window. Hopefully they mean something to you.
       Cheers
                Herbert
Herbert Niesler
Attachments:
Explain Changes.jpg ‏46 KB

Build Error: Append image and delete if possible.vi

Good morning,
I'm using LabVIEW 9.0 with the application builder and when I attempt to build my application I receive this error:
An error occurred while saving the following file:
C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\printing\ReportDocExtensions.llb\Standard Report\Append image and delete if possible.vi
Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>
I did some research and this seems to be related to saving a front panel image to an HTML file. I'm not storing the front panel image at all, nor am I storing anything to an HTML file, only Excel.
Just in case I had somehow inadvertently added it to my project (this is my first LabVIEW project and I've made all kinds of mistakes, haha) I performed a search of my project for "Append image and delete if possible.vi" and it was not found.
Does anyone have any thoughts on this? I'm not sure what other information I should post here, please let me know if I missed something.
Thanks!
Solved!
Go to Solution.

Dear Logan,
This error occurs in the saving process (before the build is complete). In the details section says:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 6 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Generic file I/O error.
=========================
NI-488: I/O operation aborted.
I repaired my LV2009 instalation and doesn't worked. The last thing i'll do is to reinstall all my NI software . I'll spend a whole day doing that.

Problem with Append Front Panel Image To Report.vi

I'm using LV 7.0 with the MicroSoft Report Generation toolkit installed. Under the Report Generation palette there exists an Append Front Panel Image To Report vi. Also on the same palette there is an Easy Print VI Panel or Documentation.vi which uses another Append Front Panel Image To Report vi located under the VI Documentation subpalette. Here is the problem; I have serval vi's that use Append Front Panel Image To Report.vi from the Report Generation palette and I have a couple of vi's that use the Easy Print VI Panel or Documentation.vi which is linked to the Append Front Panel Image To Report.vi located under the VI Documentation subpalette. Clear as mud!
This creates a conflict of intrest. In a nut shell th
ere are two vi's with the same name in different locations doing different things. I have a program with subvi's that need to call each respective Append Front Panel Image To Report.vi and that just is not working.
Is this a known issue with LV7.0 that has already been addressed and/or resloved?
Thanks.

ATC Herman,
Based on the picture you posted and what you are describing, it looks like you might have an incomplete install. What version of the toolkit do you have? Was it first installed on an earlier version of LabVIEW, or did you install it first on 7.0? Your VI Documentation Palette appears the same as if you hadn�t installed the toolkit. I�ve attached a screenshot of what it should look like. The VI in question is a polymorphic VI, which may be causing some of the confusion. If you right-click on it and select �Open Polymorphic VI�, it will show you what options you have, depending on the input. I opened both test and test1, and they appeared the same for me. I was able to have them both on the block diagram. The path to bo
th of them was C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib\printing\ReportDocExtensions.llb\Append Front Panel Image to Report.vi. The .llb ReportDocExtensions has the polymorphic VI, as well as copies of each of the possible instantiations. Make sure you have these VI�s in the .llb in that directory.
There is a KB on having the toolkit on multiple versions of LabVIEW and what files you need. Make sure you have all the files listed.
Please let me know if you are able to get to the bottom of the issue with the above information.
Thanks, and have a happy day!
Robert M
Applications Engineer
National Instruments
Robert Mortensen
Software Engineer
National Instruments
Attachments:
Report_Palettes.JPG ‏57 KB

Printed front panel graphics quality (Print Panel to Printer method vs. Append Front Panel Image to Report.vi)

LV 6.02 (or 6.1)
NT 4.0
I have a vi that the front panel includes all the information I need to print except that it is on different pages of a tab control to conserve screen space. I was attempting to programatically cycle the value of the tab control in a For loop and invoke the Print Panel to Printer method to print 7 pages of the front panel, each with a different tab page selected. The printouts were excellent quality but beginning with the second consecutive Print Panel to Printer method the on screen front panel image of the VI being printed would become jumbled (sometimes, by the time 7 printings were done, the entire front panel image would disappe
ar and a bitmap of the desktop or underlying windows would be visible in the VI's panel frame) yet the subsequent Print Panel to Printer methods continued to print the panel as they should appear. The visible front panel graphics would never return to normal and the only solution was to close the vi (in the dev system) or exe (compiled) and re-launch. I tried a lot of things (like hiding the panel to print before printing and showing it after printing) with no luck. It appears that two or more of these consecutive invoke methods caused the problem regardless of whether the tabs were cycling, or even if there was no tab control and much fewer controls on the panel to be printed than normal. I also had the same problem with LV 6.1.
Finally, I was forced to switch to the report generation toolkit vi's, I cycle through the tab pages and use the Append Front Panel Image to Report.vi to append each image to the report. This is faster and control returns to my program quicker but I a
m unhappy with the printed quality of the graphics of the front panels. They are not as high of resolution as those generated via the Print Panel to Printer method.
Any suggestions?

You might try changing the way the VI is printed by going to tools >> options >> printing. Try the postscript and bitmap settings.
Jeremy

Cluster not saved correctly in Append Control Image to Report VI

[LV8 with Windows XP]
I'm using the Append Control Image to Report VI to save the image of a control to Word (the same problem occurs if I save to Excel). This VI seems to work fine with all my controls except clusters. Not all of the contents of the cluster show up in the saved image. I have to expand the edges of the cluster way beyond the cluster contents in order for all the contents to show up in the saved image. Is this a bug? Is there a way to "realign" the contents of the cluster within the boundaries?
George

Hi,
just had a customer with the problem with this cluster picture function and I wrote a little VI that manually gets the picture, resizes it to the cluster and the rest is up to you. The only thing is, that you have to place the "zero point" of the frontpanel in the upper left corner to get the proper image.
For Users who want to upgrade: This issue is fixed with the next LabVIEW release.
Best Regards,
Andreas Pistek
~~~ Logic is a systematic method of coming to the wrong conclusion with confidence ~~~
Attachments:
better picture.vi ‏19 KB

I can't append control image to report on 1 page with appended text report

I am attempting to create a report which is simply header, experiment information, and two graphs of data. I am using a Easy Text Report and Append Control Image to Report. I have successfully printed out this report, but on two separate pages. The header info is on the first page, and the graphs on the second page. This doesn't seem to be a margins problem, as the header is very brief and the graphs aren't that large either. I would like to make this into a one page report. Any help is greatly appreciated.
Message Edited by csmrunman on 01-15-2010 10:18 AM

Nevermind. I neglected to see the Append Report Text.vi. That solved everything.

Print report and append control image to report.vi problem

why print report.vi and control image to report.vi can't executable in xp service pack 3??
before that, i use xp service pack 1. these sub vi can use successful. but after i transfer all ni file into xp service pack 3, that sub vi can't executable..why it happen???
please, help me...

When you said that you used your VIs in service pack 1 and then transferred to Service pack 3, are you referring to 2 different computers or you simply updated the computer with SP1 to SP3?
If you are using 2 different computers, were all the software and the toolkit also installed in the pc with SP3? I am using XP with SP3 and I am not having any problems with the print vi.
If you have more information, like if you get an error message, kindly post it here as well.
Best regards,
Mary Anne
.....YOU WONT LEARN IF YOU ALREADY KNOW.....

Bug in Append Control Image to Report in 8.5?

I am now at an end with this. I seem to have some sort of problem when using the Append Control Image to Report. I have a program that creates two reports. One is a condensed version, the other detailed. Both reports contain JPG images of some front panel displays. For the most part it seems to work except what ever it is doing appears very unstable. The problem seems to center around me trying to include a Multicoulmn Listbox. I create a Reference of it and then run that to my Append Control Image, just like any other image I want to include. If I probe the Reference, it appears to be correct, i.e. the name, etc. all seem right. However, what the image that gets included is a whole different graphic. Some times I will get the listbox, other times nothing at all. If I look in the directory and bring up the images, indeed, if it prints the wrong graphics, it also has created two of the ne that it includes.
Running the same program unmodifed seems to do the same thing, i.e. it always will print the wrong graphic. As I have tried different things to try and skirt the problem, I get different effects.
I have seen the same problem with other graphics as well, not just the listbox, but I can't come up with any hint as to why it does what it does.
Attachments:
LABVIEW_err.jpg ‏18 KB

I have dug into this a little further and it appears this bug has to do with creating two reports at the same time. If I only generate a single report, everything works flawless.
I placed the sections of the code that append data to the reports into a sequence so they would not happen at the same time. This seemed to have some effect, but the reports were still incorrect.
Is LabView just not able to create two reports within a single progeam?
I can work around this by creating just the detailed report for now, but it would sure be nice if there were a way to make it work.

Standard report appended image

Hi,
I'm using XPsp2, LV 2011sp1, standard report, append image VI.
The appended image appears at a low resolution (screen resolution?) when printed. Text is perfect.
If i resize the image to a larger resolution (dpi) it resizes it to fit within the margins but retains the low resolution. The auto-re-sizing results in a distorted image if it is resizes to fit the width, but does not need to resize to fit the height.
Can i increase the resolution of the printed images in the report? -to 150 or 300 dpi so they do not looks so pixelated when printed?
Thanks.

To follow up, the response from an email support request.
"Hi Blue,
Thanks for the information; it was really helpful in understanding your problem further. I've managed to print out the exact same type of response as you've been getting; the larger DPI image just comes out a lot bigger for Standard reports than the smaller DPI image. I also dragged the files into MS Word and saw that the images were resized appropriately. Interestingly enough, I set the type of the report to 'Word' and when printed, the images came out at the appropriate resolution. This means that inside of the MS Office programs, there is some internal compensation for recognition of image DPI scaling that isn't native in the Standard report in LabVIEW.
I also selected to print a 'HTML' implementation of the report. The images were again mismatched in this state.
Q: How do we work around this issue?
A: There are two options I see at this point. We can either try reconfiguring the DPI of the printer that we're printing to, or we can take a copy of the resized image in Word by taking a snap of the screen and then cutting the resized image out. I just tried this out and the resized image that I cut out from a printscreen of MS Word looks just as expected on the report.
I took a look inside the Report Generation VIs that were used for printing and I couldn't find any aspects that we could modify to alter the interpreted DPI of the images. This is because the lower level print functionality is hidden within the higher level LabVIEW Property Nodes and is therefore inaccessable from any Block Diagram code. In this regard, I don't believe that there are any direct features native in LabVIEW that as LabVIEW Users, we will be able to modify. I made a VI to resize the image in LabVIEW and then print the output, however the issue with this is all of the quality in the original image was inevitably lost.
You can head over to the LabVIEW Idea Exchange and post this feature request on the forums and get other LabVIEW Users to Kudos it; the higher the Kudos, the more change of the feature being incorporated into a newer release of the toolkit. I definitely agree that this would be a great feature and I'd be more than happy to contribute.
LabVIEW Idea Exchange -
http://forums.ni.com/t5/ideas/v2/ideaexchangepage/blog-id/labviewideas
I hope that this is okay. If you have any further questions or ideas, please don't hesitate to get back in touch. I want to make sure you're completely satisfied with the solution that we reach.
Kind Regards,
So in summary: No, you cannot adjust the resolution (DPI) at which the Standard Report Generation toolkit processes appended images.... Unless anyone knows better? ...i can not get satisfactory results from either of the suggested work arounds.
BR
Blue

No data found when display image in report

Hi,
I have a table with a blob field in it which I use to store some image (gif),
I tried to display the image in report but follow the guideline in http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/advnc_blob.htm#BCGBCHBD
but when I run the report, error
"report error:
ORA-01403: no data found"
prompt, I do not have MIME,FILENAME column in the table, so I define only
IMAGE,Table Name,Column containing BLOB,Primary Key Column 1 and Primary Key Column 2 in the report column.
Anyone has also this problem?
Thanks
Pek

Hi,
I found that the problem is there when I select the option
"Use Generic Column Names (parse query at runtime only)" in the report.
Is this a bug?
Rgds
Pek

Error when running a custom report.

The log file shows following message:
APPLLCSP Environment Variable set to :
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
AMERICAN_AMERICA.UTF8
Enter Password:
MSG-00101: CONC_PROGRAM_ID 50507
REP-0069: Internal error
REP-62203: Internal error reading the image - Unable to render RenderedOp for this operation..
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-69: MSG-00101: CONC_PROGRAM_ID 50507
REP-0069: Internal error
REP-62203: Internal error reading the image - Unable to render RenderedOp for this operation..

What is your OS? what is your version? Looks like it cannot read the image format. Please provide more details on what reports you are trying to run?

Windows App Certification Kit 3.4 error occurred while generating the report (the application will exit)

Hi all,
I've encounter a pretty big issue while trying to check if everything with my windows phone 8.1 app is all right. After creating package (*.appx) I launched Windows App Certification Kit 3.4 to run it against all the test. Each time I try I get an error saying
"an error occurred while generating the report. the application will exit" and Certification tool just crushes
I looked online for some solutions but couldn't find any. Somebody knows what is going on and how to fix it ?
Can't insert images into post because of not verified account so imgur:
http://imgur.com/ptT0cU3

Try sending it to store anyway… I have the similar issue, the kit hangs when saving result and never complete it.
Another member has same question.
https://social.technet.microsoft.com/Forums/en-US/11910167-75e1-47d8-a0fb-fb8046c57f89/windows-app-certification-kit-31-reports-failure-due-to-crash-or-hang?forum=projectsiena.
If you want to test your app, you can also send to beta store and you can get response from the testers.

Error in Append Image to Report.vi

Similar Messages

Maybe you are looking for