unwanted, reoccurring automatic recovery

[Riconquistiamola]

Hi Ton,

I was never able to reproduce this issue, but if we can get a copy of a VI having this problem here I can research the problem and, if necessary, file a CAR.

Michael K. | Applications Engineer | National Instruments

[JeffBoettcher]

I only briefly skim the subjects of the forum threads, and regretfully I missed this one until now.

Some questions for anyone experiencing this problem:

• Are you always logging into the PC as the same user?
• Does this user have write permission to its LabVIEW Data directory and all its subdirectories? (i.e. on Windows, C:\Documents and Settings\[username]\My Documents\LabVIEW Data)
• Does this user have write permission to the location where the original file is?
• If you monitor the contents of the LabVIEW Data\LVAutoSave directory both before and after selecting Recover and Discard on that VI, is there still a file in the LVAutoSave folder after doing Discard?  How about cancel?
• Do you get any error messages during the recovery process?

I'd like to do my best to help anyone experiencing this, but it might be difficult if we can't isolate the cause, and since I have never seen this happen personally, I'm having trouble thinking of what might be causing it.

[TCPlomp]

Hi Micheal and Jeff,

I think you pointed me to the right item (and I have not seen it anymore)

Recently my laptop changed from standard into domain controlled because I was having serious issues with password changing and network drive access.
This was only half done... 'My documents' moved onto a network drive, normally this should stay available to the laptop when offline (something fancy).
Now when I started working offline, LV said it couldnt find 'my documents', then when running a vi I got a 'not able to create auto-recovery message'. I created some bad code and needed to kill LV. On startup after a few times, I keep getting the 'auto recovery' (even when on-line).

To fix it I disabled the auto recovery of LV, restarted and enabled it again.

Ton

[magyar]

I am the originator of this subject. It seems that I am not the only one who experienced this phenomenon.

I am working on another machine nowadays, and  I don't have recent experience with this problem.

I did have administrator rights to all files ton the C-drive.

I did not monitor the contents of the LabVIEW Data\LVAutoSave directory both before and after selecting Recover and Discard on that VI.

If, in the future, I go back to that particular machine, I'll check on it.

[JeffBoettcher]

I understand you probably have better uses for your time, but if you'd like to try to reproduce this on your machine, try the following:

1. Launch LabVIEW, make sure AutoSave is enabled.
2. Open a VI, preferably one you don't care too much about, just to be on the safe side.
3. Drop a new control on its front panel.
4. Create a new, blank VI and run it.
5. Simulate a crash / power failure.  (Windows) Ending task on LabVIEW from Task Manager.  If prompted to save changes, DO NOT acknowledge the dialog in any way.  Wait a few seconds for the OS to prompt you to "End Now" on LabVIEW.
6. Launch LabVIEW.  You should be prompted to recover changes to the VI from step 2.  You can now examine the LVAutoSave folder to see what happens when you pick various options, and see if the problem is reproducible on your machine.

If you get a chance, let me know what you find, thanks!

[magyar]

Jeff,

I had the opportunity to simulate failure as you described it. I used the "Text Report Example.vi" and added a knob to the front panel.

After restarting LV8.2 there was an autorecovery window as expected.

I chose "cancel" and proceeded with LV.

I closed LV.

The LVAutoSave folder had an archives sub folder with a zip file in it.

When I reopened LV there was nothing unusual about the behavior.

I guess I’ll have to observe the content of this LVAutoSave folder if and when I have another spontaneous malfunction.

I repeated this by forcing the power out.

I did not see any unwanted autorecovery attepts.

Maybe the large size of the source code I was working with when the original problem was observed has to do something with it?

Anyway, I do not have any problems now.

Thank you for your time.

[JeffBoettcher]

Thanks for the feedback.

I wouldn't expect size to be a factor, but hey, with bugs, sometimes you encounter things you don't expect.  🙂  At least this one is harmless with an easy enough workaround.

I'd be more inclined to think it would be related to how you respond to the dialog, but if you also were hitting "Cancel" the time you saw the problem, then I don't have a good explanation yet.

Hopefully if someone else sees this they'll find this thread and add their experiences, and maybe I'll see it soon enough to get some feedback from them while the situation is occurring.

[TCPlomp]

Hi Jeff,

I got the problem again, and went to LabVIEW Data\LVAutoSave a few files were there, but 2 files (the ones reoccuring) couldn't be deleted (even if LV was closed). I used an Unlocker tool, but it couldn't find a process that's claiming the files.

Ton

[JeffBoettcher]

Hey Ton,

Thanks for the feedback.  I am not sure what would be causing these files to get into this strange state.  I presume that these files will not go away no matter how you respond to the recovery dialog either, correct?  Various things that should remove those files are:

1. Selecting "Recover", and then closing the recovered files.
2. Selecting "Discard".
3. Selecting "Cancel".

So we've determined that even after restarting LabVIEW these files are not deletable.  To resolve the problem, you might try restarting the computer.  Of course then we might not be able to reproduce it anymore.

Is there anything that struck you as particularly odd about the situation in which you originally ended up with these files to recover (crash / power failure / etc), or the subsequent initial recovery process?  Or did things seem to go normally?  If you don't remember that's ok, but I'll take whatever information I can get.  🙂

[TCPlomp]

None of this works (yes I tested), I have to disable the autobackup function and restart LabVIEW

To get this problem, place you %my documents% on a network drive. Get a LV crash, restart PC (without network), start LabVIEW, when  a VI is run LV will complain that it couldn't autosave. I think i'll need to contact the sysadmin....

Ton

Message Edited by TonP on 03-02-2007 10:28 AM