[ayeckley]

FWIW, had the same problem (Error 1502) occur again yesterday. This time the supposedly offending item was "Begin.VI". The solution I found was to revert to an older copy of Begin.VI that had been successfully built in the past, build it (successfully), re-implement the exact same changes, then build it again (successfully). This is the second time this approach has worked. Solution time: 4 hours including the time spent trying to diagnose the problem. Once I gave up trying to find an actual error in the VI, the time spent to backtrack and re-implement was only about 20 minutes. This will be my preferred approach in the future, obviously.

As before, the code could be deployed w/o any errors generated or issues in function, but wouldn't successfully build. It would *supposedly* build OK (no errors were generated, at least) when the "enable debug" setting was checked under the Advanced tab in the build options, but after uploading to the cRIO it resulted in a "No Robot Code" condition. Experimentation showed that the issue was not related to file or folder permissions, nor file or folder path length.