Failure: "oleautomgr.cpp" line 364 (LabView 6.0)

This failure occurred when I try to print a graph. It was working properly before. Does anyone have this failure before or know a remedy to the failure?
Thanks in advance.

Alliance Member wrote:
>
> I am using report generation tools for printing the graphs & tables &
> various texts..when I make exe of a vi which contains above Vis then
> after making exe if i run it or simply I run labview with any report
> generation vi for printing "oleautomgr" error comes which can be
> solved only by first uninstalling labview & removing "NI Reports"
> folder from windows registry, restarting pc & again installing
> labview...is there any other solution ......
Whenever you get a failure with a module name & line number, you should
try www.ni.com/failure.
In this case, www.ni.com/failure lists this error & provides a fix!
Best, Mark

Similar Messages

Failure "osupport.cpp" line 4163

I get this error while working with lab view 6.0.2. and the whole LabView shuts down. I'm using the report generation tool kit and Windows XP. What should I do to stop this from happening?

Hi Felipe
you should report this to NI support along with your VI and the LabVIEW_failure.txt file.
Maybe your VI is corrupt, so NI has the opportunitiy to fix it so you can use it and recreate the code they have to delete.
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

Fatal Internal Error on startup "color.cpp", line 663, LabVIEW 8.0

I get this error message everytime i try to open a VI (even a blank VI!).
Now i'm sut uo, i can't usa any of my VIs!!!!

I thought I should mention a couple of things regarding your last post.
I'm quite sure that the file you referenced is not the LabVIEW preferences file. The file should be located in your user directory under Libraryreferences. I'm pretty sure it's just called "LabVIEW 8.0 Preferences".
LabVIEW 8.0 was not tested for use on an Intel-based Mac. I can't say if this would be related to the problem or not.
Good luck!

Fatal Internal Error source/manager/thread.cpp line 3472 while starting LabVIEW

When I try to begin LabVIEW 7.1.1 on my mac OS X 10.4, I see the LV logo and then I get the pop-up window:
LabVIEW.app Alert
Fatal Internal Error: "source/manager/thread.cpp", line 3472
LabVIEW version 7.1.1
You will lose any unsaved work. For assistance in resolving this
problem, please relaunch LabVIEW, or contact National Instruments.
When I click on Continue, it kills LabVIEW. I also get 2 other
windows...one says Investigate Previous Internal Error...which does not
do anything, irrespective of what I click in that window.
The other window is called Controls.
The last message I see on the LabVIEW splash screen is Server: Exported VIs list ok.
The LV website says I need to make DLLs re-entrant, but I can't even begin LV to solve this problem.
Any suggestions?

Hi Enduro,
I would suggest creating a service request for this problem at ni.com/ask. The Applications Engineer will be interested in looking at the error log that is being created, so that we can determine if this problem has occurred before.
Amanda Howard
Americas Services and Support Recruiting Manager
National Instruments

Lv crashes every 10 days, "plotsupp.cpp, line 1330"

This vi continually writes to a buffer and displays on a waveform chart. Upon a trigger signal, a predefined amount of data (in the buffer) is written to a file and the vi ends. Labview is crashing every 10 days with failure message "plotsupp.cpp, line 1330". Mac G-4, OS 9, LabVIEW 6.1, 6031 I/O Card, 38 channels of data.

Hello �
What happens every 10 days? Does the program get to the same specific point after 10 days of running? What does that specific part of the program do? Does the user have interaction with the VI or is it running by itself?
The only report of this error crash we have is when the user tried to modify the labels in a control. Somehow the control got corrupted and the problem was fixed by replacing the controls in the front panel with new ones.
If this does not help, you can narrow the problem down and post a simple VI so that we can reproduce the issue.
S Vences
Applications Engineer
National Instruments

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.

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

Thread.cpp, line 1938

I got this error message when I was running my programm.
"thread.cpp", line 1938
labview version 6.1
I went to check "Task Manager", and it seemed like labview kept increasing memory its memory usage until there was not any left. so this error did not happen in the begining. It took some time.
Is this a bug of Labview6.1? Or where can I set up the maximum memory usage of this application so the computor won't be dead?
thank you.

This may be cause by a bug in your program. LV does automatic memory management for you, and it's usually pretty good about it, but if you use functions that require more memory during run-time, LV will allocate more and more memory until you run out. Good examples of this are Build Array and Concatenate String. If you use these in a loop to build a large array and do it fast, you may run out of memory pretty quickly.
Try using the profiling tools in Tools>>Advanced (I don't think they exist in the base package) to see if you can pinpoint the consumption to one of your VIs. You should also read the white paper about memory management in LV. You can find it in Help>>Search the LabVIEW Bookshelf or by searching this site.
If this is consistent and you can't solve it, I suggest you post your code.
Try to take over the world!

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?

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

Failure: "might.cpp" line 815 on LabVIEW executable

Hi,
I have a program written in LabVIEW 6.1 on a Windows XP platform. The program includes an ActiveX container that shows an Internet Explorer content window (just like the "Using the Microsoft Web Browser ActiveX Control" example found on http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123AE0CB9BF111EE034080020E74861&p_node=DZ52051&p_submitted=N&p_rank=&p_answer=&p_source=External
, but without the activex queue in that example).
After I built the executable, I was able to run the exectuable on the development machine without problem. However when my client runs it on his PC with LabVIEW runtime engine 6.1 installed, he gets the message:
Failure: "might.cpp" line 815
For assistance in reso
lving this problem, please record the procedeing information and navigate to www.ni.com/failure or contact national insturments.
I cannot find any information on might.cpp on the NI support site. Any idea of what can be done to fix this problem?
Thanks!
Dan

Hi dan,
you must contact NI support sending them the problem. "might.cpp" is a source module of LV and they can investigate the error.
Another thing you have to take into account is that LV stores the class ID and not the application. Has the client PC the same MS IE version installed? If not, the error could also result from different versions of the Active-X control.
As with the reporting Toolkit for MS Office you have to build a different version of your app for each different version of the control.
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

Failure : "resource.cpp", line 2477

When building an application on LABVIEW 6.1 on Window 98, I get the error message:"Failure : "resource.cpp", line 2477". Attached is my Labview failure log file
Attachments:
LabVIEW_Failure_Log.txt ‏1 KB

Hi Kluu,
This error appears when checking the "Do not compress target file" option when building an application. The workaround is to not check that option in Application Builder.
While in the application builder, in the "Target" tab, in "Build Options", do NOT check the "Do not Compress Target File" option.
We are currently looking into this and will soon be fixing it up.
Hope this helps.
Regards,
Pravin Borade
Applications Engineer, National Instruments

Failure: scalesup.cpp line 767

Hi,
My vi is crashing and giving me the error message:
Failure: scalesup.cpp line 767
I have isolated the problem, and it occurs at a waveform graph property node. I have the property node set for Xscale.Markervals[ ] . I'm trying to create a set of custom markers by sending a 1D dbl array to the property node. This custom marker array is the same length as the data array (600 points).
Thanks for your help in advance.

Are you using a logrithmic scale? If so, then make sure that the value of one of the markers is not zero.
If not, then what version of LabVIEW are you running? Can you take your data and create a simple VI that das that data aas the default in an array and then plots it to a graph and then does the property node? This should be pretty easy to set up so that we can reproduce this issue.
Also, bug reports such as this one are normally handled better in an e-mail or phone support request.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Failure window.cpp line 2039

Developed LV 5.1.1-Applications on Win NT4.0. Now i need to run them on WIN 2000 Systems but receive only errors while starting :
window.c line 2019 (by starting my Application.exe)
window.cpp line 2039 (by starting the LV Development system on the WIN 2000 PC)
Until now I`ve tried two WIN 2000 PC`s, different graphic drivers and graphic settings,
w/wo additional PCI-GPIB cards -> no result
Even the LV 6.0 student edition shows this error after installing on Win 2000
Any idea will be welcome
Best Regards
Markus

MarkusM wrote:
>
> Developed LV 5.1.1-Applications on Win NT4.0. Now i need to run them
> on WIN 2000 Systems but receive only errors while starting :
> window.c line 2019 (by starting my Application.exe)
> window.cpp line 2039 (by starting the LV Development system on the WIN
> 2000 PC)
> Until now I`ve tried two WIN 2000 PC`s, different graphic drivers and
> graphic settings,
> w/wo additional PCI-GPIB cards -> no result
> Even the LV 6.0 student edition shows this error after installing on
> Win 2000
> Any idea will be welcome
> Best Regards
> Markus
Does www.ni.com/failure help?
Mark

Failure : "load.cpp", line 4081

My main front panel VI will no longer open and I just get the error, Failure : "load.cpp", line 4081.
I am running an Eval version of 6.0.1 and was deciding whether to buy this product for a new project.
Given that I see from this forum that this error has been known for 9 months plus and I've lost a weeks
work I am not so sure.
It occured after I added some tab controls to the front panel, so beware.

Hi RCT,
This error occurs in LV 6.0.1. It seems that it is fixed in LV 6.0.2 and LV 6.1.
One thing you can do is ask NI to delete the insane objects for you. You have to redo your work you have done since the time the VI was correct until it got corrupt.
The other thing you can do is use a copy from a backup and redo the rest of the work.
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

Failure: "oleautomg​r.cpp" line 364 (LabView 6.0)

Similar Messages

Maybe you are looking for

Failure: "oleautomgr.cpp" line 364 (LabView 6.0)