09-21-2007 12:49 PM
11-14-2007 01:24 PM - edited 11-14-2007 01:26 PM
11-15-2007 09:21 AM
Hi svango,
Thanks for contacting National Instruments. Like mentioned in a previous post, this particular error in this situation has been reported to R&D with that Corrective Action Request ID. As it was reported for LabVIEW 8.5 and this is our latest version of LabVIEW, it will still be present when you are using LabVIEW, but there may be a workaround that you can try. This error occurs when trying to build an application out of a VI that has a static VI reference to itself. So what you should try is use the Open VI Reference function and pass it the Current VI path constant to be able to build your application. I hope this helps and good luck with your application!
11-16-2007 04:40 PM
11-19-2007 11:01 AM
Hi steve05ram360,
With respect to your question, it is a little difficult to say if I will be able to post back when there is a fix. Since this error has been reported to R&D, it is not possible for me to say exactly when it will be fixed. What I can guarantee you is that it is known and is being recognized as something to fix, but I have no way of knowing when it will be solved. So being able to post back when there is a fix is difficult to say as I do not know when it will happen and where I will be at that time. However, I do hope that the workaround is helping some and the CAR ID is for this particular bug. Thanks and have a great day!
11-19-2007 01:31 PM
Ok, thanks... I ended up reworking my application to not use the vi reference and am moving forward. Next time around, I'll check the updates to see if there is anything new for the app builder.
thanks
-steve
05-13-2020 06:55 PM
I had the same issue and found this thread with no solution. It turned out I used disable structure and some of the vis were missing inside the disable structure and those were the root cause of the error. After removing those missing vis, I was able to build the application (in my case source distribution as llb).