Compiler.cpp line 1169

I am unable to load a LabVIEW 6.0.2 VI in LabVIEW 2012 SP1 (or in SP1 f3).
I get a failure in compiler.cpp: DWarn 0xA291168F: Error: generated insane Intermediate Representation
The error is LabVIEW is 'LabVIEW needs more memory to compile this VI'.
The VI operates on Chart data (array of cluster pairs) with several consecutive For loops to perform the calculations.
There are NO chart controls or indicators in this VI --- just array and cluster inputs and outputs.
Any idea how I can get around this problem with compiler.cpp?
NI Software : LabVIEW version 12.0.1f3
OS : MacOSX

Well, just for fun, here's the contents of that VI copied into a new VI. I made two changes: replaced the subVI with In Range and Coerce, and removed a front panel cluster that was acting only as a type definition for a bundle by name, then replaced Bundle by Name with Bundle. I'm also attaching that code as a snippet. Maybe one or the other will open.
Attachments:
XY Depth Rescale.png ‏61 KB
XY Depth Rescale.vi ‏20 KB

Similar Messages

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

File 'pcprocbinding.cpp', line 1028, function 'PCDBTableCollection::FindOptimizedColumn'

The cube was compiling ok. I was using sql Server 2012 Standard.
I upgraded to Sql Server 2014 Standard.
Now when compiling the cube, without any changes, I get this error :
Internal error: An unexpected error occurred (file 'pcprocbinding.cpp', line 1028, function 'PCDBTableCollection::FindOptimizedColumn').
Errors in the OLAP storage engine: An error occurred while processing the 'Fact Inventaire Sem Past Year' partition of the 'Fait Inventaire Semaine' measure group for the 'Canac DM Ventes Produits Semaine' cube from the CanacDMVentesCondense database.

Hi Karlrw,
Glad to hear that your issue had been solved, thank you for your sharing.
Regards,
Charlie Liao
TechNet Community Support

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

The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

Nickled and dimed once again by obscure errors. This is LabVIEW 10.0.1 on Redhat EL 5.5 32-bit.
I removed an enum from the project that is also used in a typedef control cluster. Since many VIs use this typedef I have to go to each VI and save in order to remove the phantom dependencies (i.e. popup can't find enum ctl when opening VIs). In the process of opening every VI and saving LabVIew is crashing on me reliably but not everytime just after I press cancel when it tries to find the enum ctl.
Here are the errors. Sometimes the address is null....I believe LabVIEW src code should check for null/bad pointers but does not in this case.
GenNAryOp_ArrayBase : naryop, setdef? ninp=1
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xFF
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x21
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt bool, csrc=0x30
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xA
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x50
LabVIEW caught fatal signal
10.0.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0xffffffff
Upon reopening LV I see this.
The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.

Hello wbdoyle,
I'm sorry you are seeing that error. Did you close and save the type def that included the enum? This should prevent you from having to go through and save each VI that includes the type def. Are you using the System Exec VI? Also, are you performing any data acquisition with the VI you are referencing? The error you are seeing indicates that the LV compiler isn't handling something in your VI and I want to pinpoint exactly what is happening.
Thanks!
Regards,
Anna L
Applications Engineer
National Instruments

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

MDIS assertion log: A2iMultiThread.cpp" line="254" !m_hasLock

Hi MDM Gurus,
Issue: MDIS services need to be restarted once a week for the automatic import to occur
The assrtion log on our MDIS server keeps logging this message:
<Open ts-long="14:39:46 GMT, Tuesday, April 12, 2011" ts="2011/04/12 14:39:46.703 GMT" pid="***" host="*****" compile-type="WIN32_RELEASE">
<Assert ts="2011/04/12 14:39:46.703 GMT" tid="3084" entry-no="127015" file="..\..\..\GenericLibs\Base\*A2iMultiThread.cpp" line="254">!m_hasLock*</Assert>
has anyone come across this? we applied Note 1321795 - MDM 5.5 SP06 Patch05 Release Note after we were advised by a previouss OSS note raised, but now its still occurring albeit less frequently of restarting the services every day as it would not import the data automatically

this surely seems to a bug !
if this is happening in the Production server - plz raise a high prio OSS with SAP
btw : is the MDM server / MDIS running in a cluster ?? or single SID ?
thanks
-Adrivit

Fatal Internal error: "oleautomgr.cpp", line 2832

Hi,
I have a program developped with LV 8.2.1.
Now I have import this application with LV 8.5; if I run the VIs in Labview it works; when I run my program (executable version) I got this error
"Fatal Internal error: "oleautomgr.cpp", line 2832"
I got the error after I open a Diadem connection.
Another information: first time I have import the program in LV 8.5 and I have save the prj, LV ask me to overwrite all the VIs of the "Diadem addons". (Diadem connectivity); so I have uncheck "read only" in Diadem.llb and I have save the Vi.
Someone can help me?
Thanx a lot

For the community's future reference, this issue was resolved by the customer calling in for support, at which time it was determined that a Mass Compile of the VIs was necessary to eliminate the error. The process to mass compile is described here.
-Sam F, DAQ Marketing Manager
Learn about measuring temperature
Learn how to take voltage measurements
Learn how to measure current

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

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

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 error: "memory.cpp", line 593 with PXI 8175

Hi,
I have created a program with Labview RT 7.0 which makes acquisition, storage and display of data with PXI controllers 8175.
I used Datasocket for the data display on a deported computer.
Because of the number of the Datasocket tags used, instead of sending values all the time, I'm sending value for the deported computer only if the user needs to see it.
For example : if the user needs to see data, so only Datasocket tags for data display will be active, and if the user needs to see parameters values, so only parameters datasockets tags will be active. And, if the display program is in "standby" mode, almost all datasocket aren't active.
So when the user needs to see data values, he opens the data values window of the display program, and then, the datasockets tags for data value are now active, but : sometimes at this moment, the PXI stops with an "internal error "memory.cpp" line 593"!
The only solution is to manually reboot the PXI, the programmatically reboot doesn't work in this case of error. But it is far away from the displaying computer.
The error happens regularly after a 2 weeks period of standby. So I though about a memory overflow, I checked all the arrays, and none of them is growing to the infinity.
If someone knows about this problem, I will be very happy to learn about how to get rid of it!!!
Best Regards,
G Liagre
Best regards,
G Liagre

Hi Rob, Hi Matthieu,
Thank you for your reply.
I found in the database many reply about this error, but none of them were helpfull for me.
I tryed your link to the knowledge data base, but the error described there is for dll association in LabView and interface nodes.
I didn't used any interface node in my code.
The problem is that I cannot test my program on the PXI because I don't have access to it rightnow (only by remote desktop, and with a 56k modem..)
Let me give you a part of this huge code.
I suspect this part of the code to be the one which create the problem, but it's not sure.
If you find something obviously wrong, tell me!
Best regards,
G Liagre
Best regards,
G Liagre
Attachments:
Communication.zip ‏931 KB

Slide Show ERROR, Internal software\Vobulator\BlockPlanner\.cpp Line 217

I'm putting together a slide show DVD. There are a total of 7 slide shows containing 480 pictures. All pictures are jpg's about 1000X1600 pixels and 500KB-700KB each. I have 3 menus for navigation. Not all of the chapter menu buttons point to a "slide show", some of them point to a picture inside certain slide shows according to my client's requests. (example, slide show 1 contains 70 pictures. Chapter 1 points to "slide show 1" Chapter 2 points to "slide show 1 photo 50"). All slide shows are linked so that when the first slide show is over, it will automatically "end action" to the next slide show etc... All my settings are typical. NTSC 4:3 SD 720X480 progressive.
There are NO video files in my DVD at all. No timelines at all. No audio at all.
The Symptoms/problem that I'm getting is this, when I try to Preview my DVD and ALSO when I try to build my DVD, the build will go through and "build the slide shows" then after it does that, this will come up
I've read some of the previous posts (one of them is in French for cryin out loud. Had to use Bing translator and it sounds all weird). What I can gather is this,
Re: internal software error: .\Vobulator\BlockPlanner\BlockPlanner.cpp, line 217
I found out it was due to selecting an image file as the video layer
in a menu, causes the error everytime. I just paste the image in with
'edit in photoshop' instead now. But thanks."
Another person said just about the same thing... The only problem is, I have no idea what this means. I don't know what it means to "select an image file as the video layer in a menu..."
Hardware/software is as follows:
custom build:
i5 processor (4 core) 2.6ghz
8 GB RAM 1333MHz
300GB C: drive (2X150 GB 10K RPM Raptors)
1.2TB D: drive (2X7,200 RPM 640GB WD's)
Burner is LG Super multi
secondary burner is Sony Commercial Blu-Ray burner
Video card is Saphire Build (Radeon 5450 PCI-E 16X)
Windows 7 X64 Pro
All Adobe is CS5 Production package.
If I'm leaving anything out, please let me know.
HELP! and Thanks. I'd really love to fix this without rebuilding the whole DVD. Take long time.
TEX

You really gain nothing by posting the same thing twice... http://forums.adobe.com/thread/971701

Winocc.cpp line 329 - using CWGraph in MFC OCX project

I'm trying to create my own custom ActiveX control for use in a third party application. My control consists of a dialog window (CDialog derived) that I use for data display. This works fine, but if I drop a CWGraph control onto my dialog, the control crashes the app with an assert in winocc.cpp Line:329. Is what I'm attempting possible? Can anyone tell me why it crashes? I'm using VS2005. I've included a dummy project that shows the problem. I'm still sort of new to VC++ so I may very well have missed something obvious.
Thanks-
Attachments:
MyTestOCX.zip ‏4258 KB

Hi codeman,
Have you tried replacing your CWGraph control with any other common Visual Studio controls, like a button. I don't think that it is the CWGraph that is causing your application to crash. I think it is some of your code behind the project. I'd like to see if we can verify the operation with a different kind of control.
Regards,
Marty H.
National Instruments

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?

Compiler.cpp line 1169

Similar Messages

Maybe you are looking for