WANTED: workaround for error in fontmgr.cpp line 1023 when loading LV 6 VIs

Hi,
when loading existing VIs from LV6 with our new LV7Express the program (running under Linux 8) crashes with an error in fontmgr.cpp line 1023.
Is there a workaround?
Thanks.

Hi dieter,
there is normally no workaround for internal LV errors. Report the error through the support pages to NI. Together with your VIs they will be able to fix the problem.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Similar Messages

  • Internal Software Error: .\AVTreeNode.cpp, line 25 when saving a project

    Hello,
    I am trying to work with Encore DVD 2.0 on Windows XP professional (SP 2). Until now with every project I try to make I see new error messages, and my whole work consists of trying to find work arounds.
    My actual project consists of five slide shows. They are all between 1 and 2,5 minutes. Except for one, that only consists of a black screen shown for 5 seconds.
    I have a playlist that contains all slide shows. Between two of the longer slide shows I inserted the 5 second black screen. What I wanted to achieve with this technique is that I can easily change the "gap" between two slide shows by changing the duration of the black screen slide show once. Alternatively I could have added a black image as the last slide two each of the four slide shows, but then I would have to change the duration of that slide four times when I want to change the gap between the slide shows.
    Anyway, I finally tried to create the project which resulted in the CVOBUPlanner.cpp error in line 331.
    So I wanted to track down the problem by
    - deleting some of the slide shows
    - saving the project under another name
    - trying to create that project
    So first I deleted everything but the first slide show from the playlist. then I deleted all the slide shows but not the first one (and the 5 second black screen though I didn't use it here), from the project. Saved the project under another name and created it without an error.
    Then I opened the original project again. Now I deleted everything but the first slide show and the 5 second black screen slide show. Again I deleted the slide shows, but not he first and the 5 second black screen.
    I tried to save the project under another name, but now I received an internal software error: .\AVTreeNode.cpp, line 25.
    After I restarted the application I was able to open the original movie, delete the slide shows and save the project under another name.
    I still wanted to let you now because this is an error message that I have not seen before and didn't find here in this forum.
    Regards,
    Christian Kirchhoff

    There are a couple of other threads about a similar error which seem to point to a possible chapter playlist problem:
    Internal Software error ..... When 'preview from here' or Build
    Chapter Playlist play order bug?

  • Internal software error: .\EditorTemplates.cpp, line 698

    This project is due to my client tomorrow. Not thinking in my right mind I decided to install Production Studio Premium in the middle of working on a big project. I've tried to Google the error but I'm not coming up with anything:
    "internal software error: .\EditorTemplates.cpp, line 698"
    This appears while building my disc or .iso image just after reaching the "Analyzing Project" phase of the build progress.
    This project is only 2 menus with 4 total timelines. One of the menus uses both motion background and audio.
    HELP!!!!!!

    Sorry -- I just noticed that there is a thread on this error elsewhere in the forum ( http://www.adobeforums.com/cgi-bin/webx/.3bbee891/21 )Somehow when I searched for this error that thread did not show up. I'm going to take a look at that thread and see if there is anything that will help.
    Again, sorry for posting the same topic twice.
    EDIT....
    OK, having read through the other thread, I feel that it is my duty to summarize the apparent fix here. It seems that there could be one of two problems, which are discussed by two posters:
    1. "The issue was that instead of using return to last menu which is for use in a series of menus, instead I should specify the menu I want to return to. The summary is: make sure you're only giving one choice for an end action and don't use an override, and make sure to specify which menu even if there is only one when you return to a menu. When I did this it worked like a charm."...
    "'Return to Last Menu' End action for a timeline is the culprit. Don't Use it. "
    or
    2. "I hit this problem today and found taking out the Return to last menu did not help a bit. I found that *deleting the chapter playlist, then recreating it* (The same by all I could tell). Would eliminate the problem."
    Interestingly, I know that I have both of these (i. e. a playlist and the 'return to last menu' End action) in my project. I will test these fixes out and report back when I have a moment...

  • 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

  • Internal software error: .\PGCStreamInfo.cpp, line 1413

    Im designing a DVD teaching project within Encore DVD 2.0.0.48678 from the Creative Suite 2 Production Premium software system. The project is very large and complex. As of now there are only 2 separate timelines. 1st time line has 50 chapters. 2nd time line is not finished but currently has 15 chapters. Because its a teaching DVD, there are also chapter play list created for each individual chapter. I also have a countless number of menus and links to sub menus and additional video links from the chapter play list. All of my links are set and operational with all functions in the individual menus working properly. This is an ongoing project for 3 months now, with perfect results prior to today. I have used the "preview from here" function with no problems to test the links and verify the menu structures with flawless results for the past 3 months. Today I was giving a demo of my progress, when I selected the "preview from here" I received this new error message, "internal software error: .\PGCStreamInfo.cpp. line 1413". I have checked and rechecked links, buttons, playlists, chapters, end actions, timelines, basically everything I could imagine and have even tried a computer restore point from 5 days back, at this time still have not resolved this issue.
    AMD Athlon 64 3000+
    2.01 GHz 1.00 GB of RAM
    Microsoft Windows XP Home Edition Version 2002 SP2
    Gigabyte GeForce 7300 GT videocard
    Thanks for any suggestion, if more info is needed to solve this, i can provide it.

    There are a couple of other threads about a similar error which seem to point to a possible chapter playlist problem:
    Internal Software error ..... When 'preview from here' or Build
    Chapter Playlist play order bug?

  • Error 38 "thread.cpp line 1938" failure during an application execution

    I made a Labview6.1 based application that handle serial communication with six RS-232 ports. The program is intended to run 24 hours a day. After around 2 days of execution an error occurs. Here the reference:
    Error 38
    thread.cpp line 1938
    What can be the root cause of this failure?
    I'm pretty sure it's not lack of memory/CPU.

    Hi Mao,
    Be sure that all the threads you oppened are all closed.
    For example if you put an "open VI reference" don't forget to put the "close reference" at the end of the task.
    Hope it helps!
    Best regards,
    G Liagre
    Best regards,
    G Liagre

  • How to resolve Error #3: memory.cpp, line 563

    I moved my application to a new computer with Windows XP and installed Labview 6.1 from the installation disc.  When I run Labview 6.1, it allows me to open a project but, as soon as the project loads it shows the following error message (Error #3: memory.cpp, line 563).  I deleted dir.mnu as suggested but the problem persists.  The application runs fine on the old computer.  I even uninstalled and re-installed Labview 6.1 on the new computer with the same result.  What do I do now?

    I'm sorry, I'm the one that was confused... You are having a FieldPoint problem, yes?
    First make sure that the FP VIs are not stored as part of your appliction code. If it is, delete it. Next, if you don't already have them, install the latest version of the FP drivers.  If you have only the latest version of teh drivers installed and you are still getting crashes, this sounds like an NI problem.
    The sort of problem you are running into is but one of many reasons for not saving code from the vi.lib as part of your application code.
    Mike... 
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • LV 6.1, 3D Surface Graph sometimes collapses (doesn't work stably); plus blocks use of remotely controlled panel by LV run-time engine (error #26:"window.cpp", line 11518

    1) "3D Surface Graph" does not work stably; sometimes it changes its properties (e.g. plot style) without me doing anything prior to that; a couple of times it lost a complete sense so that I had to delete the graph and install it again
    2) I tried to remotely run a VI which contains a 3D Surface Graph in it. It turns out, the use of the "3D Surface Graph" somehow blocks the remote control over the panel. As a result of that, I got the following error message: Error #26: "window.cpp", line 11518 (with LabVIEW version 6.1).
    3) Is it possible to plug into the 3D Surface Graph a few plots at
    the same time since there is a built-in control "plot number" (somehow by bundling them up or putting into an array - I tried both but didn't work) or it can be done merely by use of 'case' structure preceding the Graph, where case structure decides which plot to pass into the 3D graph?
    Attachments:
    3D_Graph_ver_1.bmp ‏214 KB

    Hello mjoler,
    Thank you for contacting National Instruments.
    The following example will show you how to plot multiple 3D plots on a single 3D graph. Modeling your VI after the example may also alleviate the instability that you have been experiencing.
    http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B123AE0CBA19111EE034080020E74861&p_node=DZ52038
    As far as the error you are receiving, it's difficult to say what could be causing this. ActiveX controls embedded on a front panel sometimes do not display on a remote client because they draw and operate almost completely independent of LabVIEW. If possible, try remotely controlling your VI with a client computer that has a complete installation of LabVIEW. The error could also be a bu
    g. Try downloading the evaluation version of LabVIEW 7.0 from http://www.ni.com/labview. By doing this, we can determine if it is a bug in the older version that has been fixed in the latest version.
    Let me know how this goes.
    Matthew C
    Applications Engineer
    National Instruments

  • Error #3, "memory.cpp", line 865(V6.0) 876(V6.0.2)

    I used a VI one day with no problems, and the next I got this message - "Error #3, "memory.cpp", line 865" I did not even close the VI or modify it an anyway.
    I was first running Labview V6.0 and tried upgrading to V6.0.2 but the error continued (now on line 876). I also tried recompiling and backup copies of the VI and SubVIs, which did not work either. A suggested fix is to delete "dir.mnu", which likewise did nothing.
    To me it looks like the problem rests in the Labview "Copy" command, which I use to copy a file to another directory, because when I delete it it works fine again.
    Any suggestions would be greatly appreciated!

    Hello,
    It seems that while copying your file, memory is filling up too quickly for LabVIEW to clean it up and it's crashing LabVIEW. View the memory usage in the Task Manager to confirm this.
    LabVIEW Internal Errors (Failure in XXX.c / XXX.cpp at line YYY)
    If the Copy function is not the cause of the error, about 95% of the time, the next step is to look for DLL nodes or CIN nodes. The likely culprit is that a string or array is being handed to the C code, which either overwrites memory, or leaves the array/string data structure to an inconsistent state leading LV to overwrite memory. Anyway, this is a very common cause.
    If you eliminate that possib
    ility, the remainder are usually some sort of corruption saved in the VI, but normally those will not even load.
    To simplify it before submitting it to support, please try executing individual subVIs and see if the problem is limited to a particular VI or a smaller set of VIs.
    Zvezdana S.

  • Fatal Internal Error: "Memory Manager.cpp", line 547

    Hello,
    I am using LV 2009 and I am also getting an error as follows:
    =======================================================
    Fatal Internal Error: "Memory Manager.cpp", line 547
    LabVIEW version 9.0.1 
    You will lose any unsaved work. For assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
    ======================================================= 
    I get this error when I start executing steps on TS 4.2.1 as well as when I do "Unload All Modules" in TS. Please find the attched logs. Further, I could not run anything in TS and need to restart the PC to re-run the sequence after everytime this error occurs.
    We have transited through LV 8.0, 8.2, 8.5 and now 2009 over past 4 years for our project and this is the first time I could see this error.
    Please help.
    Thanks.
    Attachments:
    lvlog2010-06-09-10-06-07.txt ‏2 KB
    lvlog2010-06-09-18-52-36.txt ‏1 KB
    lvlog2010-06-09-19-16-20.txt ‏2 KB

    Adding on to Pritam's post:
    For the earlier "Fatal Internal Error: "Memory Manager.cpp", line 547" , we found that a couple of our dll's which were developed in LV 8.5.1 had not been recompiled in LV2009. After recompiling each of them in LV2009, and then running the same sequences in TestStand,this error vanished.
    But now again we're seeing this error, and that too only on  3 PCs systems out of 5 PCs!
    The same installer has been installed on all 5 sytems (after removing the earlier installers and running MSI Blast.exe them).
    The error now appears again, only when we try to exit TestExec.exe and another tool built in LabVIEW.
    So everything works fine and tasks are performed,etc, but when we close the window or try the exit that program, the "Fatal Internal Error: "Memory Manager.cpp", line 547" pops up.
    If we say "OK" to it, the window closes, but the Task is seen still running in the Task Manager and has to be manually terminated (End Task).
    Does anyone know what could be going wrong?

  • Internal software error: .\filespec.cpp line 130

    I have an encore project with multiple menus and videos that I finished after a year. We have been through two revisions and I have the final go ahead with 2 tweaks and I am done.
    Problem is, I try to open my encore file and it states "internal software error: .\filespec.cpp line 130" can anyone please help me?
    I do not want to start from scratch. I did a google search but did not come up with anything. I recently switched to windows x64 with a multicore system so I am going to take it home and try it on windows there. Any help would be appreciated.

    Hi
    I'm having the same problem, did you find any solution?

  • Error #3: "memory.cpp", line 639; VI used to work, now it stopped

    Hello,
    I am running LabVIEW 6.0.2. I have a rather complicated VI that used to work just fine. I have run it a bunch of times without any problems. I have not changed anything at all, and now it gives me Error #3: "memory.cpp", line 639 every time I run it. Does anybody know what could have happened?
    Thanks,
    Corey

    Corey,
    Not without seeing the code.
    Perhaps there is some memory leakage going on, or open references that cannot be resolved.
    Also, check your memory to make sure it is still working (view your RAM amount).
    Other possibilities include possible conflicts with software running in the background, or software you recently installed.
    Check your task bar, and make sure your virus protection and anything else unecessary is off. These can eat memory and processor time.
    Other than that, navigate to the site where the bug tells you to (don't remember off the top of my head) and report it to NI.
    Good luck

  • 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

  • Fatal Internal error: "oleautomgr.cpp", line 2832 when sending data by means of ActiveX methode

    I have experienced  error "Fatal Internal error: "oleautomgr.cpp", line 2832" during sending data to CAN card IXXAT iPCI-I XC16/PCI. LabVIEW communicates with that card by means of ActiveX methodes via "VCI Wrapper" which is COM object interface. Mass compiling of the project does not help. Card is initialized and configured propely. The driver card is working propely.
    LabVIEW version is 8.5
    The efect of that error is that labview completly shot down.
    I appraciate any suggetions
    thanks a lot

    Hello,
    Please try to reinstall the drivers for the CAN card, then make sure you close all references to the ActiveX control (at all levels) using the Automation Close primitive in LabVIEW.
    Regards,
    Emil

  • Why do I receive error on datasupp.cpp line 3563?

    I am running a serial communication program and often the program crashes, when I restart Labview, I receive an error message referent to the datasupp.cpp line 3563

    When LabVIEW generates a .cpp error, an internal error has occured within LabVIEW where a condition exists such that LabVIEW cannot continue execution. Generally, LabVIEW has reached a point in its internal code where it checks to see if certain conditions are true. Under normal circumstances, these conditions are indeed true, and LabVIEW is equipped to handle them. If they are not true, LabVIEW reports an internal error. LabVIEW reports the internal error and shuts down because to do otherwise would be to risk corrupting any VIs in memory.
    Unfortunately, we do not have any record of the datasaupp.cpp line 3563 ever causing an error. When LabVIEW does throw internal .cpp errors, it will store a failure log file in your My Documents/LabVIEW Data/lvfailurelo
    g directory by default. If you allow investigation of these internal errors, you can submit your error log file to National Instruments and we can see how the error message was generated.
    You can check out http://www.ni.com/failure for more information.
    Thanks again.

Maybe you are looking for