This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Error 1097 Occurred at Call Library Function Node

Updated Apr 29, 2019

Reported In


  • LabVIEW

Operating System

  • Windows
  • PharLap

Issue Details

My LabVIEW code references an external DLL. When I run my program, I get a message that says Error 1097 occurred at the Call Library Function node, but my program does not stop execution.

Error 1097: LabVIEW (Hex 0x449): An exception occurred within the external code called by a Call Library Function Node. The exception might have corrupted the LabVIEW memory. Save any work to a new location and restart LabVIEW.


This error often occurs due to an exception being passed inside the DLL that LabVIEW is unable to process. 
Check to make sure:
  • the DLL works properly outside of LabVIEW
  • the Call Library Function Node parameter datatypes are configured to match the datatypes expected by the DLL function

Error 1097 may also indicate that memory is being handled improperly by your program. This may be due to improper calling convention in your Call Library Function Node. The stdcall (WINAPI) convention expects that the DLL will handle memory usage, while the C calling convention expects that LabVIEW will handle memory usage. Using the stdcall (WINAPI) convention improperly can result in unhandled memory. The calling convention can be configured by double-clicking your node and changing the selection, as shown in the image below.


Not Helpful