Executable throws error 0x6

[David_R._Asher]

I have a LabVIEW project that I have been working on for a while now, making updates and building releases every few days.  Today I built a new executable and when I run it the following dialog pops up: 

I removed my recent changes to see if that was what caused the problem but it continues to have the same error.  I have built many version with no problems before today, so I don't understand what is causing the issue.  I can build an executable from other projects that work, so the builder is still functional.  When I press okay on the above dialog several others pop up with the same error with the lvclasses listed that I am using.  The user interface opens, but has a broken run arrow.  When the run arrow is pressed the following dialog appears:

Any help or suggestions would be greatly appreciated.

Thank you!

[Bob_Schor]

Hello, David.

     If you are a CLA, then it seems unlikely you are doing anything totally bone-headed, so I won't chastise you for not attaching code.  With probably two decades of LabVIEW experience, you must have internalized the need for using (and not ab-using) Version Control.

     What happens if you try to build "last-week's Commit"?  If it built and ran OK then, and doesn't now, it suggests it's not the code, but the environment.  Have there been any updates to Windows?  to LabVIEW?  to the PC itself?

Do you have access to another computer (or a VM) to use as a "test environment"?  Can you think of any other recent changes that I haven't mentioned?

     Please keep us posted, especially if you can pinpoint the cause of the problem!

Bob Schor

[David_R._Asher · Accepted solution]

I seem to have fixed it.  I had noticed a few similar posts about file names being too long, and I kind of remember that issue in the past.  I shortened a few absurdly long and overly descriptive folder and file names and built it again and it works now.  At least I assume that's why it started working again, though it doesn't explain why it broke in the first place, because I hadn't changed any file or folder names since the previous successful build.

thanks!

[tst]

My guess would be a compile issue and that the renaming caused a new entry to be created in the compiled object cache with the new path. At least, I know that the cache stores things by path and I never checked to see if updating a path updates the same row in the database with the path or creates a new one or recompiles.

If you run into this again, I would suggest trying clearing the compiled object caches (Tools>>Advanced) before rebuilding and possibly also force compiling the hierarchy (Ctrl+Shift+Run arrow on the top level VI).