Fatal error: protocolsup.cpp

I am getting a Fatal Internal Error: protocolsupp.cpp line 3218, when I put a breakpoint in my vi. I am using LV8.2 RT.
This happens most of the time I put a breakpoint in and causes LV to quit.
Any ideas what is causing this?
Chuck

I have the same problem when I try to step over (see log below).
Anybody have any information about this error? It looks like it was first reported over a year ago.
Last time I tried, it crashed Labview and Windows. Impressive.
Joe
#Date: Tue, Nov 06, 2007 12:34:28 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.5
#AppKind: FDS
#AppModDate: 07/25/2007 03:07 GMT
c:\builds\penguin\labview\branches\Jupiter\dev\source\server\protocolsupp.cpp(3244) : DAbort: MakeSyncCallEx: No available slots for opcodesent:1491 27=kOpSetVIState, waiting for 1132=kOpSetInstrStateAck
sent:1492 27=kOpSetVIState, waiting for 1132=kOpSet
$Id: //labview/branches/Jupiter/dev/source/server/protocolsupp.cpp#57 $
0x00F4C898 - LabVIEW <unknown> + 0
0x00AE4F38 - LabVIEW <unknown> + 0
0x00874730 - LabVIEW <unknown> + 0
0x00F49824 - LabVIEW <unknown> + 0
0x005E2553 - LabVIEW <unknown> + 0
0x0049C139 - LabVIEW <unknown> + 0
0x0049A981 - LabVIEW <unknown> + 0
0x0049C1EC - LabVIEW <unknown> + 0
0x00405678 - LabVIEW <unknown> + 0
0x0040599B - LabVIEW <unknown> + 0
0x0041EDB0 - LabVIEW <unknown> + 0
0x0053EC85 - LabVIEW <unknown> + 0
0x00F4E9C6 - LabVIEW <unknown> + 0
0x00F4C069 - LabVIEW <unknown> + 0
0x00F4C898 - LabVIEW <unknown> + 0
0x00AE4F38 - LabVIEW <unknown> + 0
0x00874730 - LabVIEW <unknown> + 0
0x00F49824 - LabVIEW <unknown> + 0
0x005E2553 - LabVIEW <unknown> + 0
0x0049C139 - LabVIEW <unknown> + 0
0x0049A981 - LabVIEW <unknown> + 0
0x0049C1EC - LabVIEW <unknown> + 0
0x00405678 - LabVIEW <unknown> + 0
0x0040599B - LabVIEW <unknown> + 0
0x0041EDB0 - LabVIEW <unknown> + 0
0x0053EC85 - LabVIEW <unknown> + 0
0x00F4E9C6 - LabVIEW <unknown> + 0
0x00F4C069 - LabVIEW <unknown> + 0
0x00F4C898 - LabVIEW <unknown> + 0
0x00AE4F38 - LabVIEW <unknown> + 0
0x00874730 - LabVIEW <unknown> + 0
0x00F49824 - LabVIEW <unknown> + 0
0x005E2553 - LabVIEW <unknown> + 0
0x0049C139 - LabVIEW <unknown> + 0
0x0049A981 - LabVIEW <unknown> + 0

Similar Messages

SOS:How to solve "internal fatal error:load.cpp line6345"?

hello,everybody. now i meet with a sharp problem in labview. when i try to save a .vi file in labview, sometimes an error information will happen which is "internal fatal error:"load.cpp", line6345". i have tried almost every way to solve this problem but falied at last.
Can you tell me how to solve this problem? thank u all!

beryllan;
Let us know which version of LabVIEW you are using. After a quick search in here at the Discussion Forums, I found that problems with load.cpp were common in LabVIEW 6, (with special mentions to the Student Edition). If that's your case, try updating LabVIEW here.
Regards
Enrique
www.vartortech.com

Fatal error splitpanels.cpp line 1148

I'm using LV 8.2.1 and I'm getting a fatal error. I've tried re-loacting my code in order to purge it, but to no avail.
The error message says "SplitPanels.cpp" Fatal error line 1148....
Any idea what's going on here?
It happens when I receive a double-click on one VI (located in a sub-panel of the main VI), relay a message to the main VI to replace the VI with another in the sub-panel.
There's a singlesequence of code which bombs LV. The same frame of my State maching can be called via other means without bombing, so there must be something in the background.....
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Unfortunately, I haven't found what I'm looking for there.
I'm not getting an unhandled error, I'm getting a Fatal error. I'm crashing LabVIEW.
I've simply disabled the particular part of code leading to this.....
It also crashes in 8.5.1.
Shane.
Message Edited by Intaris on 08-27-2008 09:02 AM
Say hello to my little friend.
RFC 2323 FHE-Compliant
Attachments:
Fatal arror Line 1148.png ‏6 KB

Fatal error (graphobj.cpp line 56 ) when opening a vi

I cannot open my vi. Labview reports a fatal error and exits. Any workaround?
Log file:
#Date: Tue, Oct 05, 2004 11:17:20 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.0
#AppKind: FDS
D:\lvworm\src\lvsource\graphobjs.cpp(56) : DAbort:
0x0070644A - LabVIEW GPIBCloseDevOrUnit + 197BA
0x007063EC - LabVIEW GPIBCloseDevOrUnit + 1975C
0x00706384 - LabVIEW GPIBCloseDevOrUnit + 196F4
0x007138B8 - LabVIEW GPIBCloseDevOrUnit + 26C28
0x009854F3 - LabVIEW TDStandardize + 18F93
0x0085D16A - LabVIEW IsDialogControlFromRef + 1A95A
0x0081ABCE - LabVIEW OMGetClassPropListIds + 3E95E
0x008561FA - LabVIEW IsDialogControlFromRef + 139EA
0x0081ABCE - LabVIEW OMGetClassPropListIds + 3
E95E
0x00855FAE - LabVIEW IsDialogControlFromRef + 1379E
0x0081ABCE - LabVIEW OMGetClassPropListIds + 3E95E
0x009DB2DE - LabVIEW TraceToolEnableLogging + 5A9E
0x00A95F4B - LabVIEW SetKeyboardHandlerProc + 827B
0x00A8E0AC - LabVIEW SetKeyboardHandlerProc + 3DC
0x00B84639 - LabVIEW WSendEvent + 229

Hi, I have tried to open with lv7.1. The result is the same error message, but the log file differs....
Regards
Tamas
Attachments:
_GA_calc_by_point_positions3_defect.vi ‏1117 KB

Internal fatal error: image.cpp

Hi all
For a couple of times this week (it was the first 2 times that this error occours) it appeared the error that you can see in the attached pic. I was watching a pretty large block diagram surfing it with the navigation window. I clicked several times the block diagram and the navigation window in order to adjust my view, when suddenly that error appeared. Then LV shut down. I launched the program again and it was all right. What was it? Some ideas? I don't want some critical error in my LV: i mean, i'm not talking about windows
Kind regards
I love the smell of napalm in the morning
Attachments:
errore fatale LV.jpg ‏71 KB

This problem has been fixed in Labview 8.1. So i suggest you to upgrade (Labview 8.2 is the last version).
If you want a work-around to the problem, here you have two possibilities:
Hide the front panel before allowing the application to exit. You can do this by creating a property node for the VI and writing 'Hidden', or 'Minimized' to the FP.State property. If your activation of LabVIEW has event structures, you can place this code inside the This VI->Panel Close event. If you do not have event structures, you should disable the close glyph on the window border and implement the above code following your main application code.
Convert your application back to a previous version of LabVIEW (such as version 7.0 or 7.1) which is not affected by this error.
Ciao!

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

I have encountered the new error "Fatal internal error fpinit.cpp line 7398

I get the error message "Fatal internal error fpinit.cpp line 7398".
I use:
TestStand 2.0
LabView 7.1
Vision 7.1
uEye USb Camera
I've included into my TestStand programm some new steps that control the uEye USB Camera.
I use following steps (all steps written in LabView):
- Initialze Camera
- Wait
- Close Camera
- Wait
I have the settings "Load dynamically" in TestStand"
If I use also the setting "Unload after sequence executes" and start the sequence I get somtimes a LabView error after running the Step for the Camera initialization. LabView is sometimes immediatlly closed. This happen at leased after 10 turns/starts of the programm. If I use the loop functions "Loop on selected steps" it happen only sometimes at the first loop. The initialize Camera Step is every time pass, if TestStand try to run the next step I get a error.( Sometimes I get also the message ActiveX Server got lost)
I detected also that sometimes in this case a constant in a other vi is emty.
Normally I use the setting "Unload when sequence file is closed" then I have the problem only sometimes at the first turn.
If the initialize Camera step is succesfull I have no problem with further camera steps.
Regards
Alexander
Attachments:
lvlog02-18-10-09-34-10.txt ‏1 KB
Copy of Error.jpg ‏76 KB
Copy of Error2.jpg ‏42 KB

Hi Alex,
I'd suggest to replace all ctl. with new ones.
Perhaps one of them is corrupt.
You will find a documentation about preferred execution system
in the LabVIEW help. I also attached this files.
Regards
DianaS
Attachments:
help1.gif ‏37 KB
help2.gif ‏11 KB

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 : "OMUDClassMgr.cpp". Line 1128

I received the following message:
Fatal Internal Error : "OMUDClassMgr.cpp", 1128
LabVIEW version 8.2.1
I was trying to build an application using the application builder.
Has anyone else had this issue? What needs to be done to fix this.

Hello,
This was reported to R&D (#4ALB7O89) for further investigation. Are you able to reproduce this problem with the same VI? Are you able to build an application with a simple VI?
Regards,
Elizabeth S.
Applications Engineer
National Instruments

Can somebody fix my corrupted subvi, error "Fatal Internal Error" "objheap.cpp"

Hello,
I have been strugling to open this file after a reboot due to not responding computer. The file is a part a larger library however, this is the part that is not responding and giving "Fatal Internal Error" "objheap.cpp" .
Does anyone know how to fix this issue or how to repair this file.
I am using a LabView 2012.
Thank you for your time.
Attachments:
Corrupted.llb ‏149 KB

Hi obarriel,
that could be a tricky job as LV2013 claims "block diagram can't be opened"!
Meanwhile you should learn two things:
- using LLBs isn't recommend practice nowadays (atleast not for storing daily work VIs)
- make a backup of your works on a regular basis (using SVN/GIT is recommended too…)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Fatal Internal Error MemoryManager.cpp

I've created a sequence file in teststand that uses the sub vi's for
reading out config files. If I run this on my development machine
there is no problem.
I tried to deloy everything onto a new target machine. I start to run
the sequence and i'm able to execute the 'Open Config Data.vi'. The
next step is to read out some data with the vi 'Read Key(String).vi'
but this creates the error. I get a Fatal Internal Error :
"MemoryManager.cpp" , line 406 LabVIEW 8.5.
What could cause this problem?

I have been struggling with this error today. It appears that under some circumstances LabView does not automatically recompile all VIs requiring referencing a typedef when the typedef is changed. In my case, the problematic routine was one in which the typedef did not appear as a control, indicator or diagram constant. An array of the typedef was an output from one SubVI that was an input to another. The first routine had a case structure around it with some cases where the output took a default value. I assume the default typedef output is the core of the problem in my case. Manually recompiling the routine (or making any code changes to it) solved the problem.
One could probably do a mass recompile of the whole VI hierarchy to solve this problem, but that's undesirable in a large program that is being developed by a team. It is at least something to try if you are running into this error.
Unfortunately I have not been able to make a simple program that reproduces this problem. I have attached some code but it does not make LabView crash. However, bad pointer dereferences are tricky things to debug because the severity depends on where you end up when you dereference. (In my production code, LabView was trying to read location 0xFFFFFFFF; Windows killed it). So this example could be causing silent corruption. Or my suspicions could be ungrounded and the bug may lie elsewhere.
I do notice that when I change the typedef and quit labview, labview offers to save the TLVI and the two subVIs that contain the typedef control, but not the routine I suspect is causing the problem. ("Routine that doesn't recompile.vi" in my example.)
This message is related to support issue "Reference#7184406".
-Rob Calhoun
Attachments:
MemoryManagerCrash.zip ‏36 KB

Fatal Internal Error : "LinkObj.cpp

Hi,
I currently upgraded the system from labview 8.0 to labview 8.0.1 and did a mass complile.
However after doing that I am getting an error message reading "Fatal Internal Error : "LinkObj.cpp", line 587" everytime I close a particular sequence in TestStand. This error never used to occur before the update.
The error seems to occur when it tries to unload a particular VI which I use to add tasks in MAX.
I have tried repairing Labview but the problem still exists.
I would appreciate any help
Kewal
Attachments:
error message.JPG ‏15 KB

OK, now it's getting comical...
I removed the second mathscript node from clasclap.vi and created a dummy LV math operation to replace it. Called the new vi clasclap_part.vi (attached) and added it to the project in place of clasclap.vi. Built the dll as usual. BTW, I'm using the standard calling convention here, not the C language convention.
RESULTS: All of the called functions return zeros, even clasclap_part.vi. But some good news: the dll isn't crashing Visual Studio anymore.
Now I'm realizing that the functions returning zeros issue greatly overshadows the reason I originally started this thread. If I don't get any response, I'll start an independent thread that someone might take an interest in....
What might be helpful here would be if someone could (hopefully easily) take the summer .vis and the clasclap_part.vi and build their own dll. Then, try to call it from VB6 and/or any other language or compiler. What do you get?
(FWIW, I never mentioned that I'm not a fan of VB or Visual Studio. LabVIEW is far superior IMHO)
Here is the revised VB code which calls the dll:
Private Declare Function Summer Lib "summerlib" (ByVal a As Long, ByVal b As Long) As Long
Private Declare Function Mathscriptsummer Lib "summerlib" (ByVal a As Long, ByVal b As Long) As Long
Private Declare Function Doublesummer Lib "summerlib" (ByVal x As Double, ByVal y As Double) As Double
Private Declare Function Clasclap_part Lib "summerlib" (ByVal x As Double) As Double
Sub Form_Load()
Dim x, y, fx As Double
Dim a, b, sum As Long
a = 1#
b = 2#
x = 1.2345
y = 2.3456
fx = 1
sum = Summer(a, b)
fx = Doublesummer(x, y)
sum = Mathscriptsummer(a, b)
y = Clasclap_part(290.01)
End Sub
Thanks,
Ted
Attachments:
clasclap_part.vi ‏276 KB

"Fatal internal error:"memory.cpp",line 593"

I need some help.
Can some please explain what i am doing wrong here. i have created a Dll from a LV 7.0 vi. The header file looks something like this:
typedef struct {
long dimSize;
double elt[1];
} TD2;
typedef TD2 **TD2Hdl;
typedef struct {
double f0;
double df;
TD2Hdl magnitude;
} TD1;
void __cdecl Spectrum(double freq, double amp, TD1 *Spec);
And i have the following code where i allocate memory and attempt to call 'Spectrum':-
TD1 *Power;
double frequency=10, amplitude=1;
Power = (TD1 *) malloc(sizeof(TD1));
(*Power).magnitude = (TD2**)malloc(sizeof(TD2));
*(*Power).magnitude = (TD2*)malloc(5000*sizeof(TD2));
(*Power->magnitude)->dimSize = 5000;
for (i=0; i<500;
i++) {
(*Power->magnitude)->elt[i] = 0;
Spectrum(frequency, amplitude, Power);
I keep getting Fatal internal error: "memory.cpp", line 593" when it tries to call Spectrum. I believe i have allocated memory correctly although i may be wrong. (I was getting 'exception' errors before). The VI i used to create the Dll contains a basic 'Function Generator' (sine wave) and a 'Power Spectrum'.
I have looked at the Knowledge base and dll examples that come with LV 7.0 and have tried setCINArray and NumericArrayResize but have not had any luck. It seems like the documentation is for LV 6.0 and 6.1.
Has anybody seen this or have any idea why i am getting this?
Thanks

> Can some please explain what i am doing wrong here. i have created a
> Dll from a LV 7.0 vi. The header file looks something like this:
>
> double frequency=10, amplitude=1;
> Power = (TD1 *) malloc(sizeof(TD1));
> (*Power).magnitude = (TD2**)malloc(sizeof(TD2));
> *(*Power).magnitude = (TD2*)malloc(5000*sizeof(TD2));
>
> (*Power->magnitude)->dimSize = 5000;
>
> for (i=0; i<500; i++) {
> (*Power->magnitude)->elt[i] = 0;
> }
>
> Spectrum(frequency, amplitude, Power);
>
> I keep getting Fatal internal error: "memory.cpp", line 593" when it
> tries to call Spectrum. I believe i have allocated memory correctly
> although i may be wrong. (I was getting 'exception' errors before).
> The VI i used to create the Dll contains a basic
'Function Generator'
> (sine wave) and a 'Power Spectrum'.
> I have looked at the Knowledge base and dll examples that come with LV
> 7.0 and have tried setCINArray and NumericArrayResize but have not had
> any luck. It seems like the documentation is for LV 6.0 and 6.1.
>
It looks to me like you are constructing arrays to pass to LV using
malloc, instead of the labview.lib functions for creating or resizing LV
array handles.
You should refer to the manual on Calling External code for details on
the construction of an array.
Greg McKaskle

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

Fatal error: protocolsup.cpp

Similar Messages

Maybe you are looking for