04-19-2013 10:21 AM
Labview 2009 f3
For some strange reason, any applications that include shared variable libraries will no longer build into executables.
I was able to build these applications without issue a week ago. However, when I went to make an updated build today, the build failed and I had to force Labview to close. When I view the build specification properties, I can navigate through all the option screens except the "Shared Variable Deployment" screen. As soon as I click on that option, the interface freezes up and I have to force Labview to close.
This problem does not occur for applications that do not include shared variable libraries.
I tried removing the shared variable libraries from the applications that were failing, but that did not correct the issue.
04-22-2013 07:30 PM
Hi,
If nothing has changed since it did work, it's possible something may have become corrupted. Have you by chance been able to try a repair install following the steps in the article here?
10-22-2013 08:27 AM
Hi,
I have the same issue with LV 2009. IAs soon as I click the Shared Variable Deployment in the installer wizard, it just hangs there and you can see in the Windows Task Manager that it is taking more memory and using 1 full CPU at 100%....
I did do a LV repair but it did not solve the issue...
Any other ideas?
Thanks,
10-22-2013 08:10 PM
I never did find a proper fix to this issue.
One day I attempted to build the application again, but this time I got distracted doing something else. When I finally checked the build status a few minutes later I expected it to still be frozen, but to my surprise I found that the application did successfully build. To this day, that particular application still looks like it is going to lock up, but about about 8 minutes later it finally takes off and builds like nothing was wrong...like every other shared variable application I have created. So I guess my only suggestion is to let the application sit for a while and see what happens.