Load error code 6 on downconverted VIs

[Florian.Ludwig]

Hi community,

in my attempt to switch back from LabVIEW 2016 to 2015 SP1, I have encountered a severe setback.

Among the many VIs I converted to 15.0, there are 20 (all belonging to classes I made) which will not open in 2015 SP1, giving the load error code 6: block diagram could not be loaded. I can still open the converted VIs with LabVIEW 2016 though, so there is a working block diagram there - just not one loadable in 2015 SP1.

Compiled code is not separated from the VIs.

I tried converting to 14.0 which leads to the same error when attempting to open with 2015 SP1.

Can anyone suggest something else I could try?

Best regards,

Florian

[GerdW]

Hi Florian,

recreate those VIs from scratch in LV2015?

And always code in the oldest LV version you need to support to avoid down-conversion as much as possible!?

[Florian.Ludwig]

Hi GerdW,

thanks for replying.

Recreating from scratch is an option - I'd like to avoid that, but at least it's "only" 20.

In my defence I didn't think I'd need to support 2015. I had made the switch and it all seemed to work fine enough, until it didn't. I only need to switch back because code stopped working in LV 2016 that worked fine in 2015 SP1 (see this thread: http://forums.ni.com/t5/forums/v3_1/forumtopicpage/board-id/170/page/1/thread-id/986723). Of course I have a backup from before the switch, but it took me many weeks to realise there is a problem, so I'd like to salvage the work I did by converting my code down to LV 2015.

[GerdW]

Hi Florian,

maybe the problems have their origin from the class membership of your VIs.

You may try to put the "core logic" of your VIs into subVIs. Then release the subVIs from the class(es) to have them as "normal"/"standard" VIs. Then try to downconvert them…

[Norbert_B]

Are these VIs "special" to all other VIs and share that characteristic? One example i refer to are specific access scope settings.

[Florian.Ludwig]

Thank you both for the suggestions.

GerdW, I'll see if I'll get around to trying that. My previous post and yours made me realise I could overwrite only the 20 broken VIs with the ones from my backup and go from there. Most of them probably haven't changed at all. Only the big ones have. 

Norbert_B, some of them are public, some protected. I'll keep my eyes peeled for a common characteristic.

Best regards,

Florian

[Florian.Ludwig]

Update:

I was in error when I said that only those 20 VIs are affected - them being in a class just meant that they displayed load error code 6 already when opening the project. After replacing them with files from backup I noticed other files are corrupted too, those aren't in a class.

One thing I noticed: The down-converted files really are significantly smaller than they were before the conversion and than they were when backed up originally (as though something was missing) - and still I could open everyone I tried to in LV2016 (bd and everything).