Error 1097: LabVIEW Crashes Reporting "Got Corruption with Error 1097 Calling Library" in Crash Log

Updated Oct 23, 2018

Reported In

Software

  • LabVIEW 2017 Professional

Issue Details

When I try to open a LabVIEW Project LabVIEW Crashes. After checking the crash log I see it report 
Got Corruption with Error 1097 Calling Library, followed by the name of some of my VIs in my project. 

Error 1097 occurred at an unidentified location
Possible reason(s):
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.

Solution

Navigate to the VIs listed after the error statement in your project and try to open them by themselves. If they are able to open, resave them and close out of LabVIEW. Then retry opening your project. 

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.