Problems with get latest from label

[rgkeefer]

When a piece of code is ready to be deployed we create a label. Lately, when I go to get the latest version of the code from a label created, I get an error saying "Get Latest Version failed for some files. See the messages window for details." The messages window says:

"Local file update for Util/Generic.vb failed: VaultClientOperationsLib.VCDiffException: CRC mismatch after applying delta (server CRC: 2752831503, computed CRC: 797532123)
at VaultClientOperationsLib.WorkingFolder.UpdateHiddenFileContentsFromDelta(VaultClientFile file, String deltaFile, Int64 baseVersion, Int64 targetVersion, UInt32 targetCRC)
at VaultClientOperationsLib.UpdateThread.ProcessCommand(UpdateThreadCommand command, UpdateThreadCommandResult& outputResult)"

However, It will work if I get the latest version and then do a get by label. What would cause this to happen?

[lbauer]

There may be corruption in your local cache files.

See this post for more info:

http://support.sourcegear.com/viewtopic.php?t=1314

[rgkeefer]

I used the diagnostic tool and found that my baseline was corrupted. Once I deleted all _sgbak folders etc.. and re-opened vault everything worked fine. However, in a few days I do a get latest from label and have the same problem. What causes my baseline to continually get corrupted?

[sterwill]

Do you store your _sgvault folders inside your working folders (there's an option in the Windows Forms client to store them there, which is off by default). If so, do you often perform recursive find-and-replace-in-files operations (Visual Studio has this feature)? It's possible a recursive find-and-replace would be modifying the files in the hidden folder.

Also, have you set any non-default EOL styles for these files?

[rgkeefer]

I dont store working folder data inside working folders and I have never performed recursive find-and-replace-in-files operation. I am not sure what non-default EOL styles are so I doubt that I have changed that...

[dan]

It would be helpful to know how the baseline file is different from what it is supposed to be ("corrupted" in this case just means the file was changed and no longer matches the right version in Vault).

One way to check this would be to figure out what version the baseline is supposed to correspond to, and do a diff, and see how it is different.