05-27-2013 05:56 PM
I have a slightly annoying problem that has been re-occuring the past month or so. Every time I start LabVIEW I get the following error messages:
Error occured updating the mutation history for Progam (2).lvclass. All values of this class in controls and constants will be reset to the default value
The same error appears for Page (2).lvclass, Chart (2).lvclass, Worksheet (2).lvclass and Workbook (2).lvclass.
It slows down my LabVIEW startup time by at least 3-4 minutes every time, which is quite annoying. I imagine the problem is occuring when it populates my existing projects, and in one of these projects contains the problem lvclass files. But I did a search of my ProgramFiles\NationalIntruments folder and my work directory and didn't find any files of those names. Just wondering if any one had any ideas on how to fix it?
Thanks!
05-28-2013 07:01 PM
Hello areth,
This looks to be a very rare error related to object-oriented programming in LabVIEW. Object-oriented programming is relatively new in the LabVIEW world, so our support/error documentation is still catching up.
Are you using any object-oriented features in your code? If so, can you elaborate? Do these errors occur when opening any LabVIEW VI? Do the example VIs which ship with LabVIEW still cause the errors?
I will do my best to track down more information about this error.
Cheers,
Andy C.
Applications Engineering
National Instruments
05-29-2013 10:50 PM
Okay, seems like I found the problem. Yes, to answer your question, most of my LabVIEW programming is OO, using GOOP mainly.
I also imported hundreds of LabVIEW libraries where these lvclass files were, they were in ImportedLib\DataLogger\LabVIEW widgets\ActiveX
It's not code I've written, but I don't see why including these files was necessary in the repo, oh well. To get rid of the error I just removed those files and the mutation error stopped appearing. What's still a little confusing is why these files were being accessed on LabVIEW startup. I can imagine it necessary to load these files when the project is opened, but seems weird when it's just populating the existing projects list.
Oh well, thanks for looking into it Andy, files were not in the NI folder which explains why I didn't find them on my first attempt.