09-07-2012 10:17 PM
I'm Using LV2009...also got the same problem...hsm can u give me ur email...i'll send you the error Vi....can you help me pls...thanks.
09-07-2012 10:45 PM
yeah...at last, i already fix it after upgrade with LV2009_f3DevAndRTEPatch....thanks all for the tips....it save my 3 days work...fuhh...thank God....xD
09-11-2012 03:09 AM
I can confirm that in my case the sollution using the connPaneRecoveryMode=True key works with LV2011 SP1, but not without Service Pack 1.
10-17-2012 09:44 PM - edited 10-17-2012 09:46 PM
I inherited files in an LLB from some older version of LabView
I am using 2012 and have the same problem.
I have seven different files that I am trying to recover and have resaved all of them with the change to the .ini file with no success.
Does anyone know a way that consistently works?
this problem for me occurs only in the exe file, and not in the development environment.
10-18-2012 02:22 AM
Hi AliasesAreDumb,
What do you mean it only occurs in the exe file? When you try to execute it?
If you post your files, I can have a look into them.
Cheers, RMathews
10-29-2012 08:51 AM
Hello!
Please fix my VI too, if it not so hard for you
11-06-2012 12:19 PM
I am having the same problem. If you could, please fix this vi too. It's attached.
11-19-2012 03:40 PM
Hi,
Got one of those. This morning I modified and made an executable of my vi. Since then I couldn't execute or even open the vi with, as a result, this error. I can open the sub-vi used though. So, I got my backup vi (from friday...so this was the same I did work on this morning) and I couldn't open it either this time...same error! But I did open it this morning! If anyone could try to fix it for me, I'll be really happy. I'm developping in Labview 2009 SP1. Thank you very much in advance!
Salut,
Michel
11-20-2012 02:54 AM
Here are the fixed VIs.
You can fix it also yourself by:
Instructions to fix a corrupted VI in 2011
1. Close LabVIEW
2. Add connPaneRecoveryMode=True to the LabVIEW.ini file (-The LabVIEW.ini file is located in the National Instruments folder>>LabVIEW 2011>>LabVIEW.ini)
3. Open the corrupt VI.
4. Push Ctrl+A on the block diagram and the copy and paste to a new VI.
5. Save the new VI.
6. Close LabVIEW and remove the ini token (VERY IMPORTANT)
7. Restart LabVIEW and load the new VI and verify it is correct. Save
Especially when you see a cpp-Error when opening the VI, make sure that you copy the VI into a new one. Then you can save it without problems.
Cheers,
RMathews
11-20-2012 08:09 AM
Thank you very much!
If anyone has a solution for this in Labview 2009, I would be very pleased.
Salutations,
Michel