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?

Similar Messages

  • 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

  • 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

  • How do you remove a compatexport.cpp line 38 error in LV7.1

    when running TestStand - Runtime Operator Interface I keep getting compatexport.cpp line 38 error in LV7.1
    Has any body got a solution
    ken

    Hi Ken,
    No that's not right you should have a LabVIEW *.exe.
    Have you also mass compiled all of the VI's that you are using in your sequence?
    http://digital.ni.com/public.nsf/websearch/A4753F1937860F2386256F2E006A89C2?OpenDocument
    http://digital.ni.com/public.nsf/websearch/3BECF8BBAEE613FC86256BC8006FDC52?OpenDocument
    Above are 2 links that show some solutions to the same problems you are having.
    Have a look at these and see if they help?
    In the meantime (as I don't actually have 2.0.1 installed) I'll gett looking for more info.
    Thanks
    AdamB
    Applications Engineering Team Leader | National Instruments | UK & Ireland

  • 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

  • LV crashes when I try to save a VI - "fpsane.cpp line 269 error"

    Dear LV users:
    “Fpsane.cpp, line 269 error”
    I have this error when I modify the VI and try to save it. Often I run it once and save it without problem. When I modify it again and try to save it, the error appears and LV crashes.
    First I made a 6.0.2 upgrade and later I followed the “solving troubles” procedure at NI home page, like empty the TEMP directory and so on.
    Later I sent my VI to NI support and I received the confirmation that they were able to reproduce the error, but not able to isolate it. Also they wrote that “Maybe can be a problem with the charts” and “it could be a bug in LV 6.0.2 which is fixed in LV 6.1”.
    They saved my VI as a 6
    .1 version and there were no problems (any error).
    The problem is:
    “ LV 6.1 is the next release (newest version) of LV and it will be released this year (the date is not fixed). That's not an update like LV 6.0.2 but a new version of LV. It must be purchased”
    So I have a trouble here. I have some VIs that contains some parts in common. Now they are crashing too. I’m not confident anymore to make tests and modifications, since LV will crash again. What I’m doing after run my VI is exiting LV and open the VI again. Only after I can realize (and save) the modifications. This way is really a pain in a neck....
    Please, can someone tell me a good way to isolate this problem or to solve it? I really don’t want to wait LV 6.1 nether to buy it to solve this “bug”....
    Thank you in advance
    Rodolfo
    OS: Nt4 sp 6
    LV 6.0.2

    Dear LV users
    Sorry for not have included the VI.
    "test time save format.vi" is a learning program that contains some ideas to be used in another one. The error (fpsane.cpp) that appears here also was detected in LV 6. On the first time after grouping/edit some controls.
    This error occurs when you modify the VI and try to save it. Often you run it once and save it without problem. When you modify it again and try to save it, the error appears. This is the same problem that happened with 2 other VI, even with one LV original example (after grouping).
    The same error happened in another computer (also running NT4). All libraries were rebuilt during the installation of LV 6.02 and the TEMP directory is empty.
    I hope that this vi will help us.
    Thanks ag
    ain
    Rodolfo
    Attachments:
    Test_time_save_format.zip ‏92 KB

  • Anyone ever seen an eventoracle.cpp line 370 error when dealing with an ActiveX control?

    I'm dealing with an ActiveX control in LabView 7.0 that allows me to input video / audio from a USB webcamera. The ActiveX control also allows for the playback of the AVI files that are recorded from the webcam. During playback, I occasionally get a eventoracle.cpp @ line 370 error that is hard to diagnose and hard to reproduce. Any ideas? I do have the ability to move to LabView 7.1.1 if needed, but I have not tried that yet.
    Chris Davis

    hi there
    you can adjust the user event data type to your needs. for example you can add a string "source" to the events data. additionally you can pass the "user parameter" to the callback vi to specify its location. see attachment below.....
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"
    Attachments:
    MSCOMCTL_Toolbar_EventSource_LV7.1.llb ‏102 KB

  • Undo.cpp line 3067 error when scrolling listbox

    In my application, I initialize a LV multi-column listbox as empty (Item Names set as an empty string array). Then I start writing to this property (Item Names), and once in a while, when scrolling down in the listbox, LV crashes and I get an 'undo.cpp line 3067' error. Any ideas? I thought it may be an array initialization problem, so I init it now with a string array much larger than what I plan to write to it. I get the same crash.

    vituning,
    Are you scrolling around in the multi-column listbox, then deleting all or most of the contents. The error probably happens when you try to undo this action or when you try and scroll the listbox again? If so, before you delete the data, programmatically scroll the listbox to (0,0) or so that atleast valid data will be shown. This should avoid this error.
    Randy Hoskin
    Applications Engineer
    Nationsl Instruments
    http://www.ni.com/ask

  • Compatexport.cpp line 33 error

    upgraded to 6.1 and I am getting the error compatexport.cpp line 33. I have installed MS visual C++ but I am not sure how to fix the problem.... and I have tried...

    Hi
    Check this:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/89ebd24839ef5d0286256b4c0077d8d7?OpenDocument
    Hope this helps
    Luca P.
    Application Engineer
    National Instruments
    Regards,
    Luca

  • LabVIEW Real-Time and Remote Front Panel MemoryManager.cpp line 437 error

    Hi all,
    I'm using a smartcamera (NI 1742) with LabVIEW Real-Time 8.6.
    When I look at the Front Panel with the web browser and I close the browser or I Stop the executable, I always get this error: MemoryManager.cpp line 437. I've checked if someone else had this error, but I guess I'm the only person who got this error. I saw someone who had the MemoryManager.cpp line 406, but mine isn't on this line.
    The application works well, but when I got the error, I need to reboot the smartcam to get it works. In my application, I use the Modbus library and I read/write binary file in the hard disk of the smartcam....
    Anyone knows the solution?
    Thank you very much
    Stephanie

    Hi again,
    Still didn't find the problem on my side. Here's a picture of my code. If I put the code surrended in red at place (1), I don't get the error, but if I put the code at place (2), I get the error. Why oh why....?
    I get the error when I close the browser or click Back button of the browser or Stop the application with the red dot or stop the application with the Quit button on my front panel.
    This morning I found a post on this forum about getting an error using Property node and Remote panel (http://forums.ni.com/ni/board/message?board.id=170&message.id=252705). I did what they suggest: wire the property output to an indicator and it works (disable "Enable automatic error handling dialod" didn't work... I don't know why)... until I put extra code in my VI. 
    I really need help please!
    Thank you
    Stephanie
    Attachments:
    MemoryManager line 437 error.JPG ‏228 KB

  • Failure "linker.cpp", line 2302

    How to solve this problem?

    Hi Sasha 1,
    Yes, you will first have to uninstall NI-DAQ that was shipped with LabVIEW. Make sure you have no reference to NI-DAQ on your system. You will then want to install NI-DAQ 6.1 on your system (which is the last driver to support your board).
    What probably happened was that you installed NI-DAQ 6.1 over NI-DAQ 6.9.2 and the problem is that the LabVIEW VIs for DAQ still referenced the old driver. Therefore when LabVIEW tried to call them at run-time, you got the linker error since the driver no longer existed on the system.
    You might have to go through a couple steps to clear things correctly. You might have to uninstall NI-DAQ 6.1, reinstall NI-DAQ 6.9.2 and then uninstall NI-DAQ 6.9.2 (remove reference from LabVIEW) and th
    en reinstall 6.1.
    It might simply be easier to remove all NI software on your system by uninstalling it from Add/Remove Programs and then reinstalling LabVIEW without the DAQ driver and then install the NI-DAQ 6.1 driver.
    Anyway, hope that helps. Have a good day.
    Ron
    Applications Engineering
    National Instruments

  • LabView 8.5.1 crashes at splash screen "appentrypoint.cpp, line 74 error"

    Been using it for a while.  Updated to lv2011 but need to be able to still use 8.5.1.  After upgrading found out the earlier version is not compatible with the fieldpoint 6.0.10 drivers that updated my 6.0.1 version.  So, I uninstalled the 2011 LV and 6.0.10 fieldpoint drivers.  I reinstalled the fp 6.0.1 drives from an original CD.  When I ran LV8.5.1 the above error occurs during the splash screen and LV ends.  I uninstalled 8.5.1 and did a new installation from the original CD and I still get the same error.  Would really like to get LV8.5.1 working again with fieldpoint.  Thanks.
    Attachments:
    lv error code.JPG ‏103 KB

    Hi jmw50290,
    I see that you've tried uninstalling and reinstalling LabVIEW 8.5.1, but have you tried doing a repair installation?
    Here are the steps to do so:
    http://digital.ni.com/public.nsf/allkb/fe6b641e86e55af2862576de00038001?OpenDocument
    Repair does things that regular uninstall/reinstall do not do, so it's worth a shot.
    Sincerely,
    Bogdan Buricea
    Applications Engineering
    National Instruments
    Bogdan Buricea
    Applications Engineer
    National Instruments

  • CVOBUPlanner.cpp, line 332 error - What is that?

    I've put up screenshots of the error message both from one project on a Mac and a different project on a PC.  Does anyone know what that means?  I am suddenly getting this error on both systems and it is freaking me out.

    The "vobulator" is the (licensed, not Adobe) Sonic program module inside Encore that works to convert MPEG video to the VOB format on a DVD... your message indicates a problem with a title
    Of course, the interface between the Sonic modules and Encore's error reporting has been a LONG standing complaint, so there is no read indication of WHICH title (or font?) is causing the problem
    Adobe/Jive have a BAD title for the SEARCH THIS FORUM function
    Go back to http://forums.adobe.com/community/encore and, in the area just under Ask a Question, type in
    vobulator
    You may now read previous discussions on this subject... be sure to click the See More Results at the bottom of the initial, short list if the initial list does not answer your question

  • Linkperm.cpp line 63 error

    Windows XP Sp3,
    Labview 8.6f1
    a vi file can open in labview 8.5,but can't open in labview 8.6 
     attachments is err log
    .need help
    帖子被芒果派在 12-16-2008 08:50 PM
    时编辑过了
    Attachments:
    Temp.zip ‏11 KB
    未命名.JPG ‏26 KB
    lvlog12-17-08-10-47-14.txt ‏2 KB

    But has Adobe plans to open source PixelBender3D? Can you say something about this?
    Adobe has no plans to open source PB3D. That's as much as I can say.
    Bob

  • Internal software error: .\vobulator\titleplanner\cgopgrouper.cpp, line 401 when burning DVD with sl

    I am burning a DVD that has 10 slideshows. Each slideshow is treated as a chapter. I have burned DVDs in the past using this method with no problems. Now, with this project I get the following.
    internal software error: .\vobulator\titleplanner\cgopgrouper.cpp, line 401

    This error came up again (the first time i had to rebuild), and i figured out that it had to do with a clip i had in a timeline that needed trimming, and would not butt up cleanly to the preceeding clip. i am assuming that the chapter point i inserted did not fall on a GOP, and generated this error.
    when i took that clip out of the timeline and put it in it's own seperate timeline, the disc burned with no problem.
    hope this help someone else skip the frustration i had.

Maybe you are looking for