10-16-2014 09:18 AM
Hi All,
I installed LV2014 about a month ago and in that time I have got "LabVIEW: Unexpected file type" error about 15-20 times now. I was using LV2012 previously and only saw this error about a couple of times in 2 years, but in LV2014 I almost see this error everyday. I am using P4V as my source code control.
Is anyone of you also getting this error regularly?
Ritesh
10-16-2014 09:33 AM
Ritesh,
to what file types are you referring? Does it affect VIs as well as controls? Are you sure that the files have correct extensions (.vi, .ctl, .vit, lvlib, lvclass, ...) or is it something like .vi_, .ctl_, ...?
Another option could be file corruption. Do you try to use file diff tools? Merging?
Norbert
10-16-2014 09:40 AM
Hi Norbert,
I am only having problems with VIs. All other files are OK(project, controls, etc).
No, I am not using any merging or diff tools. I am confused as to why this problem is only occuring on my system? All my peers are using the same LV version and have same hardware but they don't seem to be having this issue at all.
Should I re-install my copy of LV2014?
10-16-2014 09:43 AM
Can you check if this also happens with VI files which "separate compiled code from source file"? You can set the option in the VI, save it, push it into SCC and the pull from a different client.....
Norbert
10-16-2014 09:45 AM
I'd recommend a LabVIEW repair but maybe there is a simple solution.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
10-16-2014 10:02 AM
I'll try that and let you know if this works or not. But we never "separate compiled code from source file", so even if this solution works, I am afraid I won't be able to use it.
So should I repair/re-install LV or are there any other things which I can try to resolve this issue?
10-17-2014 02:04 AM
@LVCoder wrote:
[..] But we never "separate compiled code from source file", so even if this solution works, I am afraid I won't be able to use it.
Why is that? This is a property of a VI. So you can create a simple tool to change this setting for existing VIs. You can set an option in LV which will automatically set this option for each new VI you create.
Norbert