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.

Similar Messages

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...

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.

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

Just one needed particular GoDaddy web hosting account button link gives error in FF but ok in Pale Moon and IE

Greetings:
I've searched but am unable to find a clue. Using Win 7 Home Premium (updates current) on HP DV3T-2000 64-bit.
Recently (possibly after upgrading to FF 14), on godaddy.com on my web hosting product page, clicking the 'Launch' button throws a godaddy error pg. All other launch buttons operate normally, as do 'all' the buttons (including the tricky one) in Pale Moon and IE.
I have several times cleared the cache and deleted all g-d cookies through options - show cookies; then closed the browser and restarted the machine. I then disabled all add-ons, tried the above again, no difference so have reactivated the plugins (which were and are current as to updates).
Here is the text from the godaddy error pg:
"Error
There was an error in the application. We apologize for the inconvenience. This error has been logged and reported.
Click here to go back to your account list."
The word above [Click] 'here' usually does not work either. Below is the url from the address bar: (When going to the url on a clean new tab, the error page pulls up without the 'Click here to go back to your acct list' ):
https://hostingmanager.secureserver.net/error.aspx?aspxerrorpath=/AccountPanel2.aspx
(However, people without a g-d acct will not be able to navigate to the web hosting product page.)
Thank you very much for your help.
PS:
This list of Installed Plugins was auto-filled into the text box below the question text box. I do have more plug-ins than this in use which I can supply if needed. Thank you again!
* Shockwave Flash 11.4 r402
* Adobe PDF Plug-In For Firefox and Netscape "9.5.2"
* Google Update
* Shockwave Flash 11.3 r300
* The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
* NPRuntime Script Plug-in Library for Java(TM) Deploy
* Next Generation Java Plug-in 10.5.1 for Mozilla browsers
* GEPlugin
* 5.1.10411.0
* NDS Player Plugin
* npPCShow Plugin
* Windows Activation Technologies Plugin for Mozilla
* Logitech Device Detection
* E-centives Coupon Activator
* Coupons, Inc. Coupon Printer Plugin
* Coupons, Inc. Coupon Printer DLL
* Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
* np-mswmp

Hi hedera, when you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
(1) Bypass Firefox's Cache
Use Ctrl+Shift+r to reload the page fresh from the server.
(You also can clear Firefox's cache completely using:
orange Firefox button ''or'' Tools menu > Options > Advanced
On the Network mini-tab > Cached Web Content : "Clear Now")
(2) Remove the site's cookies (save any pending work first) using either of these. While viewing a page on the site:
* right-click and choose View Page Info > Security > "View Cookies"
* Alt+t (open the classic Tools menu) > Page Info > Security > "View Cookies"
If you can't access the relevant domain without it closing, you can edit the domain at the top of the dialog in order to call up a list of its cookies.
Then try reloading the page. Does that help?

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

Labview version 6.1 failure:"linker.cpp", line 2302

I have the labview version 6.1 failure:"linker.cpp", line 2302 fault.
Does any one can help me please ?
Solved!
Go to Solution.

Actually HeapPeak existed as far back as LabVIEW 4 or maybe even 3. However it is not usually helpful for linker errors as that is something in the LabVIEW compiler itself. HeapPeak can be sort of useful for Insane errors to locate the element that the compiler considers insane (and consequently delete and/or rewire it).
If this is a recent error on a VI that used to work before, it is most likely related to a corruption to the VI and the best course of action is to replace the VI from a backup (source code revision control would be a great advantage here). If it is something where no previous (working) state is known about, then it is going to be a tough cookie. This version is 14 years old and eventhough I still have some installation of that version somewhere it is several years ago that I started that up for more than some accidential reasons. I'm pretty sure NI would need to do some archeological work nowadays to come up with a system they could use to replicate such an error and the OP would need to be a pretty high profile customer that they would go through that sort of effort.
Maybe it is related to this error. It is the closest available in the publically accessible list of errors. A complete recompile of the entire source code tree is definitely one of the first actions to try. It may fix the problem or run into even more errors that could maybe point into a more specific location. Upgrading to a more recent LabVIEW version is another possibility although hampererd by the fact that the currently shipping version isn't officially supporting XP anymore and that the Vision software is one piece of software that underwent serious changes in the course of time and an update from 6.1 to the most recent version is most likely not a seamless operation.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Receive "Fatal Internal Error: Linker.cpp, line 1926 when run executable.

Hi, I use invoke node to call multiple subvi.vit, it work fine under .vi but when run under an executable I receive this error:
Fatal Internal Error: 'linker.cpp", line 1926
LabVIEW Version 7.0 You will lose any unsaved work. For more assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
Any suggestion will be very appreciated

Hi David,
What you are seeing is a known issue when calling LabVIEW 7.0 VITs from
an executable or DLL if the VITs include any Express VIs. It can happen if you
try to load
multiple instances of that template VI using VI Server.
There are a couple of workarounds for this issue:
Take
all the express VIs that are inside the template VI and turn them into
static subVIs. You can do this by right-clicking on the express VI and
selecting "Open Front Panel"; then save the express VI as a normal
subVI.
Build the entire application into a single executable, which will force all of the express VIs to get compiled as static subVIs.
Don't use the runtime engine at all and always run your application in development mode.
Let me know if the workarounds fix your issue, thanks.
Good luck!
- Philip Courtois, Thinkbot Solutions

Linker.cpp line 2071 error

Gentlemen,
does anyone know what the message "linker.cpp line 2071 error" stands for (under labview 7.1.1 & XP)?
we are building an medium-size application, and experiencing that annoyance without any real hint about what causes crash.
Message Edited by olivierproditec on 02-06-2007 09:05 AM

Hi,
Do any of the VI's or subVI's have names similar to existing VI's in the palettes?
After how many tests does the crash happen? (Is there any way to predict when the crash will happen?)
Does it always crash at the same point in your application?

Crash at linker.cpp, line 6323

Hello,
LabVIEW version: 8.0
I am experiencing a reproducible crash when trying to open a certain vi. The crash results in labview shutting down completely, without any error message. This vi worked before, but I was doing some small modifications, and I was changing the folder structure where my subVI are saved.
When restarting labview, I get the following message: "The last time you ran LabVIEW, an internal error or crash occured at linker.cpp, line 6323" . Does anybody know what this error means, and how I can recover the vi that crashes on opening?
Thanks in advance for help,
Johannes

Hi Johannes,
such error lines can be avoided when disabling parts of codes and find so why and where the error comes.
When you can´t open the vi anymore then attache it here and i will try to repair it.
Sometimes it gives crazy objects in code whose cause strange behaviours in vi. For that best is to delete it or use new blockdiagram and copy old code in new diagram.
Therefore its also important to save a backup (every day, hour - depend on amount of changes) from program when modify it.
Best Regards
Johann

ICWC: Is it possible to create a link in a message in the error line

Hi,
after saving a service order in the IC WebClient the success message (including the object id) is shown in the persistent header area of the ICWC - in the error single line.
Is there a possibility to have a link in this area? I want to create a link onto the object id to directly get into this order again.
Thanks for your help.
Regards,
Ben

Hi,
thanks for your response. Just for the understanding, in my case there are no error messages displayed in the error line. The only visible message is the success note "service ticket XYZ is saved successfully". After saving the ticket correctly we have to navigate to a different view. Changing this is not possible.
So the new client requirement is to create a link at the "XYZ" (object id) in this error (success) message. But I think there is no possiblity to get a navigational link or a usual html-link at that place.
Maybe you got some more ideas?
Thanks and best regards,
Ben

I have the error: "failure: datasupp.c line 531" with LabView 5.1.1. Why?

I have the error: "failure: datasupp.c line 531" with LabView 5.1.1. Why?
I use WIN 2000.

Srieng,
The datasupp.c failure can be caused by several reasons, we will need a detailed description of the operation you were making before this error happened, what is inside the VI that gave you this error, has this VI worked before, etc. Please contact us with this information, you can find the steps to email us at www.ni.com/ask , please do so and we'll review the details you send to us to determine the causes and probable workaround. Thanks!...
Nestor Sanchez
Applications Engineer
National Instruments
Nestor
National Instruments

Failure: "linker.cpp", line 3386

When I open the VI, a pop up error linker.cpp @ line 3386 and d the Labview will crash and go out. I created a password for the VI.
Windows 98
LV 6.0.2

Sajen -
Is there any way you could post the VI so that I could see the error first-hand? My first thought is that your VI somehow got corrupted, and if that's the case, there will unforunately be little chance to recover it. I assume it was opening okay before; do you recall what changes you made to it between that time and the time it stopped opening?
Eric S.
Applications Engineer
National Instruments
E. Sulzer
Applications Engineer
National Instruments

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

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.

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

Similar Messages

Maybe you are looking for