Image.cpp error line 11035, LabVIEW 6.0

I recieved the error image.cpp, line 11035 and cannot find the patch to fix this error. The program shuts down when I try to print. Where do I find the correct patch for this error in Windows?
Thank you.

Hi, I believe that this problem was solved with patch 6.02 see: release notes for 6.02
Hope that this helps,
Erik van Dijk

Similar Messages

Labview 6.0.2 patch does not remove my "image.cpp" error

I have an industrial PC with the following characteristics:
* Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours only option)
* ROBO 608, Industrial SBC motherboard with onboard video driver, from Chips and Technologies, 69000; 2MB onboard video memory
The standard VGA driver is the most recent driver, and in fact the only one available for this hardware.
Labview 5.1 runs without problem on this machine, but when I loaded Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error, line 4150" every time I tried adding a graph to the front panel. Changing the screen acceleration properties did not make any difference.
Though I have gone back to version 5.1
for the time being, my application would benefit substantially from the current version.
Are there any fixes for this, or is Labview 6 simply not compatible with VGA screen drivers?
Thanks,
Jo

I have LV6.0.2 running on an Arcom SBC with the Chips and Technology 69000
HiQVideo 2MB display chip. This chip is not capable of rendering 3D graphics.
I have noticed the CPU will go to 100% usage if I open a sub-VI panel with lots
of the new 3D graphics on it, as the display chip passes rendering off to the
main processor.
Perhaps you could try replacing the LV6 3D graphics with the older versions
that are available on the Controls pallet. At 16 colors the new graphics look
terrible anyway.
I am running the chip at 1024 X 768 screen resolution and 65K colors with
no other problems.
Regards,
Alan Brause
"Jo" wrote in message news:[email protected]..
> I have an industrial PC with the following characteristics:
>
> * Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours
> only option)
>
> * ROBO 608, Industrial SBC motherboard with onboard video driver,
> from Chips and Technologies, 69000; 2MB onboard video memory
>
> The standard VGA driver is the most recent driver, and in fact the
> only one available for this hardware.
>
> Labview 5.1 runs without problem on this machine, but when I loaded
> Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error,
> line 4150" every time I tried adding a graph to the front panel.
> Changing the screen acceleration properties did not make any
> difference.
>
> Though I have gone back to version 5.1 for the time being, my
> application would benefit substantially from the current version.
>
> Are there any fixes for this, or is Labview 6 simply not compatible
> with VGA screen drivers?
>
> Thanks,
> Jo

Image.cpp error

When I try to print the labview panel & diagram on my new canpn pixma iP1000 printer I get the following message. I am using LV6.0
"image.cpp error" in line 11035. Please contact ni.com. Anyone can help!

hi labview 1958,
please look here:
Failure: image.cpp, line 11035 in LabVIEW 6.0
Greets!

Windows LV6.0 running on Linux Wine: config.cpp error (line 404)

Have anyone tried to run LabView (Windows version) under Linux using the Wine "emulator"?
Trying this on Debian Woody, with a Win98 install of LabView 6.0 returns:
config.cpp error (line 404)
I tried to search for such a file on both Win/Linux partitions: there's none.
So how am i gonna check this line 404?
Any clue would be strongly welcome!

I agree with Labviewguru about getting Labview for Linux. The only
problem is that you have to dish out $2000 or $3500. They don't have a
Base package.
I'm not sure if NI recomends a particular window manager but I do know it
will run on any of them. In an extreme case I used it on a PII 233MHz,
64MB ram, and a 300 MB disk. It was a Slackware distro using the fvwm2
window manager. Ran great. Presently I run it with Gnome.
My point is that if you have to buy a LV for Linux license, at least you
can save money buy putting it on a machine that's been used as a paper
weight for several years.
-kevin
In article <[email protected]>,
"Labviewguru" wrote:
> I don't believe you can run LabVIEW in an e
mulation environment. There
> is too much system control that LabVIEW needs a handle on to be able to
> run on an emulator.
>
> The reason you are not able to find and troubleshoot that file is
> because it is part of the source code for LabVIEW, and doesn't exist
> except in a super secret vault which may or may not be located in Austin
> Texas...
>
> Are you aware that there is a version of LabVIEW for Linux? I believe
> that they recommend running KDE or similar GUI, but check on the support
> website for that at ni.com/linux.
>
> I hope that was enough of a clue...

Failure: "image.cpp", error 11602

I'm developing an application in LabView and with the Web publishing tool I can visualizethe results in Internet. The problem is that I open the explorer (Netscape or Internet Explorer) the following message appears in the screen: "Failure, "image.cpp", error 11602, please contact with NI" and the explorer is close... It's labview 6.1

eddie wrote:
>
> I'm developing an application in LabView and with the Web publishing
> tool I can visualizethe results in Internet. The problem is that I
> open the explorer (Netscape or Internet Explorer) the following
> message appears in the screen: "Failure, "image.cpp", error 11602,
> please contact with NI" and the explorer is close... It's labview 6.1
A good general starting point is www.ni.com/failure . Worth looking at
the specific tips (if any) for this error, and the general tips.
Mark

CPP error line 638

Hi I'm having problems with the CPP ERROR at line 638, my application includes profibus and vision. In the past when I had CPP ERRORS I had found if I sequenced the profibus VI this would eliminate the problem, however the problem has returned. I thought maybe it would be the IMAQ for the vision, so I bypassed the vision altogether, it is still in the code but not currently called or used. This hasn't helped either, I was wondering if the issue could be with too many VI's running at the same time, perhaps a memory allocation problem, but I don't know at this point.
This has been most frustrating I'm running out of I deals
Thanks
Jeffery Orn

Hello Colorado,
Normally when you are starting up LabVIEW after a crash or another error happens, LabVIEW will give you the cpp file name and the line number. You then have the option to investigate the error. This will send a report to NI so that we can work on finding why the error happens and what we can do to fix it. You should probably send that error to NI if you have not done so already.
Since the cpp file and the version of LabVIEW is missing from you post, you may want to include it. It would probably be helpful to others who may have run into this error.
I hope this helps.
Steven T.

Linker.cpp error @ line 2075 w/Labview 6.0.2 and Appl. Builder

So frustrating! The libraries run in the debugging environment just fine. No errors and two minor warnings. I have to constantly tweak and upgrade these libraries because each has about 40 VIs and are rebuilt on average two times a week. The executables are used at a dozen places and I can't place the developer system on each computer, that is what the Builder and the Labview runtime engine is for.
About a month ago after doing very minor changes in one VI I rebuilt the library into an executable using the same build file and BANG, I get this linker error. After acknowledging Labview disappears (stealth crash). Well eventually I figured I had to copy the diagram of the VI I had changed (yes, complete with changes) to another blank VI. After deleting the old VI and renaming the new (it used to be blank) VI, I rebuilt it. Everything was fine.
Well I have tried to rebuild frequently after each change and save often several copies back a month but somehow this has been futile as the error is back in both libraries. In the two libraries I maintain there are as many as 20 VIs identical between the two libraries. I make a change in one VI in one of the libraries then use the library manager to copy it to the other library. This has worked hundreds of times over the last year and half. Well somehow the problem has come back in both libraries and I can't isolate the bad VI.
Obviously one (or maybe more!) of the VIs are put together wrong but Labview doesn't detect it. I don't use any fancy linking to anything other than DAQ and SERP drivers, everything else are simple VIs (just Labview code) with only the Labview supplied VIs talking to DLLs. I have tried my little cut and paste trick with the last few changed VIs but it didn't work. I tried to use Application Builder to build VIs seperately but that was useless. I tried elminating the lastest changed VIs from the library and rebuilding but to no avail. It fails approximately 1/4 to 1/3 into the build process bar indicator but the Builder doesn't say what file it is building so I can't relate it to any specific VI. Tried relating the bar position to a latest changed list and an alphabetical list but that was inconclusive.
This issue is currently being worked on by NI support but I want to try the resources of the developer community because this is such a rare problem with big implications (at least to me).

OK, NI support came through! If the library is mass compiled the typedef in my controls won't mess with the linker. Labview 6.1 solves this problem.
Since my email to NI support got returned I'm not sure they received it. The message is: it worked and thanks.

I am gettign objheap.cpp error

i had a cluster ( pretty large one ), i added few more controls to the cluster. when i tried to open the main vi where this custer is a contol in the FP, further the cluster is used for processing(updating , reading etc)in the code.
When i try to open the main vi with the modified cluster i get objheap.cpp error and the labview closes by itself when i press ok. What could be the reason for this problem.
Is there any precaution i need ahere to when working with large clusters.

Did you get a line number? That would go a long way to finding the reason for the error.
I believe that your VI has become corrupted due to the number of controls on your front panel. Not counting the controls in the clusters, how many objects do you have?
The following link points to another link that discusses the interal errors of LabVIEW. It might help.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000007510000&ECategory=LabVIEW.Datalogging+and+Supervisory+Control

Stop labview application from MS VC got internal error: image.cpp line 11450

Hi:
I need to control a labview application (It's been compiled as exe file)from my MS VC program. I tried using PostMessage(hWnd, WM_CLOSE) from whithin my program as MSDN suggested method to stop an application
cleanly. However, when i put my program in debugging mode and run it step by step, the LV program generate an internal error "image.cpp linexxxx" after it reached that PostMessage() call. in run mode , the Labview app simply ignore the WM_CLOSE message sent from my program.
So is there any other ways to stop labview application from VC program?
Thank you!
ls

> So is there any other ways to stop labview application from VC
> program?
You can use ActiveX. Turn the server on for your built app, open a
connection from VC, and use the app or VI properties to get LV to exit.
Greg McKaskle

Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph

NOTE: This IS a duplicate post from the Breakpoint. Text slightly changed. The post in Breakpoint can be deleted. All comments should be placed in this thread.
I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..
I have an existing graphs (qt 6) which originally had 2 cursors. This occurred while trying to add the third cursor.
Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while. However, I do recall seeing this problem when creating the original cursors, but not to this extent. Plus I don't remember the original error message from that time.
I needed to add one more cursor to the existing graphs. As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message. Tried it 3 times, same result.
Here are the steps:
Shut down the PC, went for a coffee, rebooted the PC. Opened the LV project, opened the VI. Immediately went to the graph properties to add the new cursor by doing the following steps:
Right click graph indicator icon on block diagram.
Select Properties.
Click on cursor tab.
Click on Add
Select Cursor 2 (3rd one, newly created)
Change color
Select cursor as a line
Remove checkmark for "show cursor"
Click OK
I need to do this to 3 other graphs, same steps. And as soon as I get to the step before clicking OK, I get the error message.
I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties). But I've had this problem before when creating the first two cursors.
Is it a bug? Anyone else seen this? Using LV8.2. And the message is right about LOOSING ALL unsaved work!!!!
Here are more observations:
Tried creating a new one on the second graph. As soon as I clicked on the color, it crashed!
See the error explanation below. It is really clear, now anyone can solve it    LOL!!... According to the error log, there's a bad image out there
.\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
$Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
0x007A81E8 - LabVIEW <unknown> + 0
0x007A7BDB - LabVIEW <unknown> + 0
0x00829D74 - LabVIEW <unknown> + 0
0x008546CD - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0081B9C8 - LabVIEW <unknown> + 0
0x0081EB9A - LabVIEW <unknown> + 0
0x0084D9D4 - LabVIEW <unknown> + 0
0x00854663 - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0085F7A1 - LabVIEW <unknown> + 0
0x00BBACDD - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
0x0085AA46 - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
I observed the title bar after making changes to the properties. I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes". Saving was also much slower than usual. I suspect, the program never got to placing the star before saving occurred. However, I am noting everything.
After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
Does anyone have a clue at what causes this? Has anyone seen this before?
Thanks,
RayR

Hi Donovan,
I can't remember seeing this elsewhere. When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps.
I will let you know if I see this in the new vi.
Thanks!
RayR

Fatal Internal Eorror image.cpp 错误

我的一个程序打包成EXE后，在调用Exit退出labview时会弹出个错误框：Fatal Internal Error : image.cpp line 12727。如果直接在VI运行则时一切正常，labview能安全退出，请问是什么原因？
Labview 8.0

Hi
I also have a similar kind of problem, but in my case the exe was working fine for quite some time. say almost a year or so.
There are few screens which i am taking the front panel print otion in my software, when i click print on a particular screen, it pop-up this error
Fatal Internal error "image.cpp" , line 13192, labview version 8.2.1. you will loose any unsaved work, to resolve this issue relaunch labview or contact national instruments.
Once i click ok, it shuts down the software & i have to start the application again
For all the other sceens in the same application .. the same function is working fine.
Now unlike zhdo77 problem, my problem gets resolved once i reinstall the software, or sometimes by reinstalling the device drivers in the PC. But when i restarts my PC the problem appears again.
Now, my Q is ... how come the same exe was working fine for last one year, i faced this problem 2-3 days back only.
& what are the probable causes.
Message Edited by Rajan_77 on 07-02-2009 05:36 AM
Thanks & Regards,
Rajan

What is memory.cpp at line 1038?

We have been running the same test in LabVIEW for a few years. Now all of a sudden, we are starting to get a memory.cpp error at line 1038. The test normally runs days at a time (~2 weeks), but we are getting this error after about 18-24 hours. Any ideas of what could cause this? Could this be caused by any Windows XP hotfixes? We are using LabVIEW 7.1 on a windows xp machine.

I've already checked out that particular site for info. And we do open and close files in our tests. And we do have quite a few loops. But it has worked with no issues for a few years and much longer time spans (and also more open/close files and loops). So after the error occurred on our only two machines (with exact set up) that run LabVIEW 7.1 (the rest are still on 6), we rolled one back to a date before all of the hotfixes occured and we have had no problems since. The second machine had an issue with rolling back so IT came and reinstalled XP. The problem is that they install an updated version and we cannot install an older one. It has Service Pack 3 in it and I think there are some hotfixes that came along with it that are the source of the problem. But I can't gaurantee it. Hopefully we'll figure it out soon.

Load.cpp error

i fail to run my VI and it shows load.cpp line:4081 failure. what happen?

There are number of threads on this error. Here are some:
Failure : "load.cpp", line 4081
Failure : load.cpp in line 4081
failure at load.cpp in line 4081
Is
there a fix yet for error load.cpp line 4081?
They all happen when you try to open in LabVIEW 6.1 a VI, that has some tab controls on its front panel, and that was developed in the student or evaluation edition version 6i.
If you send me the VI that causes the error, I may be able to recover it. You can either post it here, or send it to [email protected]
Zvezdana S.
National Instruments

Lvinit.cpp error

I've installed NI-VISA and Labview using kernel 2.6.18 and each time I launch Labview the splash window appears for a second or so, then the application craches with the error message:
Fatal Internal Error : "lvinit.cpp", line 1553
LabVIEW version 8.2.1
this happens with both root and normal user. I looked for the lvinit.ccp file but it doesn't even exist in my box.
Any help?
thanks in advance,
G.

Hi Giuseppe,
thanks for the hint. Now it works again.
I summarised what I've done for future reference.
I've downloaded a 2.6.16 kernel, compiled and booted.
then I've installed NI-VISA packages with
alien --scripts <package>.rpm
dpkg -i <package>.deb
in the order listed in the NI-VISA INSTALL script
once done I launched updateNIDrives (don't know if was necessary)
then I've done the same for labview 8.2.1 packages
next: I'll try to install NI-488 and NI-DAQ
G.

Error while opening LabView files - Bei der Weitergabe des Befehls an das Programm ist ein Fehler aufgetreten

Hy Forum
Some times ago i had some troubles while opening files in labiew....
I want to open a LabView file (no matter if *.vi or *.lvproj file) from a network path (mapped network drive). The Windows User Account Control (Windows 7, 32bit) appears to asking me for giving access to my system settings! Oops, never seen this before, pressing yes button....
Ok, but after this the following error message appears:
I don't know what the correct message in english is
"An error occurred while executing this command"????
"Bei Weitergabe des Befehls an das Programm ist ein Fehler aufgetreten"
The LabView Getting Startet windows will be opened, but not the desired vi or project. Even if i try to open a project from the getting startet window or from the windows explorer, just the UAC window and the same error message.
Easy as it is, just remove the "run as administrator" options on the compatibility settings of Labview and it will run without UAC confirm.
And also files on network drives will be opened.
Hope this would be helpful..

Hi Dominik,
thanks for posting your experience here. This may help someone down the line.
LabVIEW should indeed not normally be run as admin as it works fine in Win7 when run as a standard user.
Regards,
Joseph Tagg

Image.cpp error line 11035, LabVIEW 6.0

Similar Messages

Maybe you are looking for