jjbloomfield

Using LV 2012 SP1, I had this exact error too. A previous post that mentioned type defs jogged my memory that one of my most recent edits was changing a "strict type def" cluster to a "type def". This cluster was nested twice in other strict type def controls. I made the change by directly opening the control rather than opening it though the nested structure of clusters. This seems to have broken the build spec. I went back and opened the control through the nested structure of clusters, made a cosmetic change so that it could be saved, and re-saved each level of the nested control. The build then worked. So the lesson for me was if you have nested type defs, be careful to access and save all affected controls through the nested structure.