Build failed - error 7

[BowenM]

So, I've got a fairly large project (few thousand VIs) that I've built multiple times.  No problems.  I just made some changes in one of my classes (all minor bug fixes) and went to rebuild and it throws an error.  For the life of me I can't figure out what would cause it.  I'm running LabVIEW 2016 f2.

Things I've tried:

-Rebooting the computer

-Changing build path

-Building on different computer

I've been through the settings in my build and see nothing odd. I'm clearly missing something or did something stupid - I can't for the life of me figure out what it would be though.

Edit:  Oh, and response to common solutions I've found...

-I'm not using the Report Generation Toolkit.

-I do have dynamically linked VIs, but I have gone back to my build and verified they are always included.

-No hardware changed.  The project calls some of the VeriStand API but no direct drivers.

-Program does run...

[PiDi]

Try clearing compiled object cache (both User and Application Builder - https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/project/viobjcache-dialog.html )

[perhult]

Not sure if any of this helpful, but:

- Have you tested forcing a recompile? (Ctrl + Shift + Run)

- Does any part of the file hierarchy have a too long path names?

- Are there dll/.Net/ActiveX calls? Can you try to disable those parts of the code and try to build?

[aputman]

Check this post.  This goes back to Labview 2012 and maybe earlier.  I hope it's not the case but it may be rearing its ugly head again.

[BowenM]

Thanks for all of the replies.

PiDi:  No luck.

perhult:  

 - I did try a mass recompile of every VI in the project folder.  No luck.

 - None of the path names should have changed... it was just bug fixes.

 - Yes... I call all 3.  I can try disabling the calls later if nothing else seems to work, but I haven't touched any of that code for months now - I don't see that impacting my build.

aputman:  I verified folder wasn't open and tried to rebuild.  No luck.  I've also tried building the modified project on a different computer (which had built the project before) and it failed again.  Clearly something is messed up in the project somewhere, but I have no clue what it could be.

[aputman]

Check any express VI's that you may be using.  I had it happen where those get corrupted and I had to recreate every one of them.  Now I just avoid them completely.

[BowenM]

---

@aputman wrote:

I just avoid them completely.

---

Ditto 🙂

[PiDi]

Enable logging and check out when exactly the error occurs:

This should help you narrow down the problematic VIs.

I've also attached a dirty version of low-level builder, which might further help you find the problem (it shows the log of builder operations - probably you'll get the same results as logging option above, but still it's worth trying...).

[paul_cardinale]

Check that any files from a previous build aren't set to read-only.

Check that you have permission to write to the destination folder.

[BowenM]

Log file showed it is some typedef control that won't save... but I still can't figure out why.

As for file permissions or read/write settings - that isn't it.