LabVIEW
"Project or Library file is corrupt" upon opening project file
Solved!
Hi! My LaqbView 2019 crashed and then upon opening the project file I get message project or "Project or Library file is corrupt".
Any suggestions how to heal it?
Hi Alex,
@Alex2019 wrote:
Any suggestions how to heal it?
Options:
- Get the latest working version from your SCC (Source Code Control) system. Ready.
- Get the latest working version from your backup. Ready.
You don't use SCC or backups?
Now you learned about the importance of both: use them from now on!
Usually when that happens, you get an option to reload from an autosave. (That feature is turned on by default.) I'm surprised you didn't get this option the first time you opened your project after the crash...
@billko wrote:
Usually when that happens, you get an option to reload from an autosave. (That feature is turned on by default.) I'm surprised you didn't get this option the first time you opened your project after the crash...
Correct. LabVIEW will create backups every so often of unsaved files that are open. When you save or revert or close and decide to discard changes, those backups go away. How often are the backups made? I have no clue. But after a crash, when you load LabVIEW, you should have had a recovery dialog come up asking what to do with the backups.
Did this happen after merging from a repository? If both you and someone else both worked on the library and made commits, most SCC systems will outsmart themselves and try to merge them into something it thinks best represents both changes - which is almost never correct - and results in a corrupt file. A library file is just an xml file, so SCC will treat it as a text file and try to merge it as such.
The best way to avoid this is to let SCC know that lvproj and lvlib should be treated as binary; therefore, no merging will take place, and you get the yellow triangle of a conflicted file instead. You mentioned yellow triangle on another file, so this is what I think happened.
@billko wrote:
Did this happen after merging from a repository? If both you and someone else both worked on the library and made commits, most SCC systems will outsmart themselves and try to merge them into something it thinks best represents both changes - which is almost never correct - and results in a corrupt file. A library file is just an xml file, so SCC will treat it as a text file and try to merge it as such.
The best way to avoid this is to let SCC know that lvproj and lvlib should be treated as binary; therefore, no merging will take place, and you get the yellow triangle of a conflicted file instead. You mentioned yellow triangle on another file, so this is what I think happened.
The only way to resolve this conflict is to choose one committed version over the other, and have the loser take the change and live with it - i.e., fix the library to reflect his changes, also. Then be careful when you are making commits when working in the same area of code as someone else.
