LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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
0 Kudos
Message 1 of 34
(5,615 Views)
Hi Chuck,

I am not sure what could be causing this, but there seems to be another customer who has experienced similar behavior.  R&D is currently looking into this issue.  My recommendation is to choose the Investigate Now option the next time you receive this error.  This will send National Instruments an e-mail with the log file which will then be forwarded on to R&D.  The more information they have about a specific error, the more likely it is that they can determine the cause and find a resolution to the issue.

Please let me know if you have any further questions.  Best of luck on your application, and have a wonderful day!!
Regards,
Ching P.
DAQ and Academic Hardware R&D
National Instruments
Message 2 of 34
(5,596 Views)

Hi Ching,

 

My dev pc can't do email, but here is a copy of the log:

 

####
#Date: Thu, Dec 21, 2006 4:15:05 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.2
#AppKind: FDS
#AppModDate: 07/27/2006 21:08 GMT

 

.\server\protocolsupp.cpp(3218) : DAbort: MakeSyncCallEx: No available slots for opcodesent:135195 27=kOpSetVIState, waiting for 1132=kOpSetInstrStateAck
sent:135196 27=kOpSetVIState, waiting for 1132=kOpSetInstrStateAck
sent:135197 27=kOpSetVIState, wait
$Id: //labview/branches/Europa/dev/source/server/protocolsupp.cpp#29 $
0x01009A28 - LabVIEW <unknown> + 0
0x006906D8 - LabVIEW <unknown> + 0
0x009B10E3 - LabVIEW <unknown> + 0
0x0100694E - LabVIEW <unknown> + 0
0x006208B2 - LabVIEW <unknown> + 0
0x004CCB39 - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004D7CD8 - LabVIEW <unknown> + 0
0x004DBA95 - LabVIEW <unknown> + 0
0x004DBD50 - LabVIEW <unknown> + 0
0x0055EE37 - LabVIEW <unknown> + 0
0x0100BD36 - LabVIEW <unknown> + 0
0x010091E9 - LabVIEW <unknown> + 0
0x01009A28 - LabVIEW <unknown> + 0
0x006906D8 - LabVIEW <unknown> + 0

Thanks.

Chuck

0 Kudos
Message 3 of 34
(5,587 Views)
Hello Chuck,
 
This was reported to R&D (#42TCTSSQ) for further investigation earlier this fall.
 
Happy New Year!
 
Janell R | Applications Engineer
0 Kudos
Message 4 of 34
(5,557 Views)
I am also getting the same error under very similar circumstances. It occurs when I insert breakpoints and then single step over individual VIs.
 
Tony
0 Kudos
Message 5 of 34
(5,510 Views)
Hello Tony,
 
This was reported to R&D (#42TCTSSQ) for further investigation earlier this fall.  I have included your comments in the R&D report.

Have a wonderful day!!
Regards,
Ching P.
DAQ and Academic Hardware R&D
National Instruments
0 Kudos
Message 6 of 34
(5,492 Views)

Any updates on this issue? I am experiencing the same problem when using "step over".

My development machine can not access internet, so here's the log generated by this error:

 

####
#Date: Fri, Jul 20, 2007 3:59:04 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.2
#AppKind: FDS
#AppModDate: 07/27/2006 11:08 GMT

 

.\server\protocolsupp.cpp(3218) : DAbort: MakeSyncCallEx: No available slots for opcodesent:460 27=kOpSetVIState, waiting for 1132=kOpSetInstrStateAck
sent:461 27=kOpSetVIState, waiting for 1132=kOpSetInstrStateAck
sent:462 27=kOpSetVIState, waiting for 1
$Id: //labview/branches/Europa/dev/source/server/protocolsupp.cpp#29 $
0x01009A28 - LabVIEW <unknown> + 0
0x00696DB7 - LabVIEW <unknown> + 0
0x009B10D6 - LabVIEW <unknown> + 0
0x00620077 - LabVIEW <unknown> + 0
0x004CCB39 - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004D7CD8 - LabVIEW <unknown> + 0
0x004DBA95 - LabVIEW <unknown> + 0
0x004DBD50 - LabVIEW <unknown> + 0
0x0055EE37 - LabVIEW <unknown> + 0
0x0100BD36 - LabVIEW <unknown> + 0
0x010091E9 - LabVIEW <unknown> + 0
0x01009A28 - LabVIEW <unknown> + 0
0x00696DB7 - LabVIEW <unknown> + 0
0x009B10D6 - LabVIEW <unknown> + 0

0 Kudos
Message 7 of 34
(5,034 Views)
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
0 Kudos
Message 8 of 34
(4,903 Views)
Hi,

I'll go ahead and include these in the report to be investigated by R&D, as mentioned earlier. This KnowledgeBase article describes general troubleshooting tips for these types of errors. Sorry for the inconvenience this has caused you!
Amanda Howard
Americas Services and Support Recruiting Manager
National Instruments
0 Kudos
Message 9 of 34
(4,884 Views)
I had the same error, I'm also using Labview RT 8.5, with WinXPpro,
I put a breakpoint and get a fatal error that makes my computer crash

Protocolsupp.cpp Line 3244

Any suggestions???

Here's the log


####
#Date: Mon, Dec 17, 2007 8:07:45 AM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.5
#AppKind: FDS
#AppModDate: 07/25/2007 02:07 GMT


c:\builds\penguin\labview\branches\Jupiter\dev\source\server\protocolsupp.cpp(3244) : DAbort: MakeSyncCallEx: No available slots for opcodesent:933 27=kOpSetVIState, waiting for 1132=kOpSetInstrStateAck
sent:934 27=kOpSetVIState, waiting for 1132=kOpSetIn
$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

0 Kudos
Message 10 of 34
(4,791 Views)