Fix LabVIEW Code generation failed to execute

[JimSi]

I'm using LabVIEW 2011. I try to use DAQmx assistance to generate one pulse signal from my USB 6259. LabVIEW popped out an error message "LabVIEW Code Generation failed to execute"

I try to reinstall LabVIEW 2011, but the error is still there. Please help

[JÞB]

Try repairing NI DAQ.  The driver may have gotten corrupted.    

[JimSi]

I re-install DAQmx. but the problem is still there.

[Marand]

Hello JimSI,

Did you follow the next steps?

1. Remove LabVIEW 2011 and NI-DAQmx from your computer
2. Install LabVIEW 2011
3. Install NI-DAQmx 9.6.1

Regards,

[JimSi · Accepted solution]

Problem is gone after re-install LabViEW and DAQmx.

thanks

[williamlweaver]

Hi All: 

Same problem here.

LabVIEW 2012 64-bit

NI MAX 5.5

Failed to execute LabVIEW Code Generation after configuring Express VI for Data Acquisition.

Academic Site License... IT has installed over network.

I'm guessing the fix a wipe and reinstall?

Thanks! 

[PTerro]

Hi williamlweaver,

You can try the steps above or you could try force reinstalling over your current installs.  Make sure to force reinstall LabVIEW before you force reinstall DAQmx.  Here is a Knowledgebase article on force reinstallation of our products;

http://digital.ni.com/public.nsf/allkb/ADD22E807D5A12AD862579EC00760F79?OpenDocument

[williamlweaver]

Thanks, Peter T!

I will give it a go with our IT department and report back here.

We've been using LabVIEW in our teaching labs since 2000 and this is the first time we've run into the problem.

Thanks for the quick reply,

-Bill  =]

[Barionics]

I have been getting exactly this problem with the 'LabVIEW code generation failed' message, but with LabVIEW 2017 and DAQ 19.6.  Allowing for this being an old thread, does anyone have a better solution to the DAQ problem than the drastic, uninstall and reinstall everything option? 

   Regards,

         Ian

[Dylanboy]

FYI, I got the same problem as you with LabVIEW 2020 and Max 20.5.  All I do is use the "repair" option in "Programs & Features" instead of uninstalling the whole NI package.  It fixed.