I am trying to use Show Differences... on the folders in my repository. I use the settings, "The current version in the repository now" and "Recursive"
I run into two different errors.
The first one says the path name is over 260 characters long and invalid. We understand this one, but is there any work around?
The second one is more troublesome.
Exception of type VaultClientOperationsLib.GetLatestVersionFailedException was thrown.
This error happens on pretty much every folder we try.
We have Vault 3.0.7 and all of the data we attempt on was imported from VSS.
Thanks for any help in advance,
-intelligent
Errors when using Show Difference on folders
Moderator: SourceGear
-
- Posts: 2
- Joined: Wed Jul 20, 2005 9:30 am
The path length is a constraint of .NET. More here:
http://support.sourcegear.com/viewtopic.php?t=1965
The only workaround would be to re-organize your tree and/or working folders.
Can you do a Get latest from that folder?
Is there an error in the Vault server log file that corresponds with the client-side error?
http://support.sourcegear.com/viewtopic.php?t=1965
The only workaround would be to re-organize your tree and/or working folders.
What diff options are you using for your folder diff: are you comparing the working folder verson to the last get; repository . . .?Exception of type VaultClientOperationsLib.GetLatestVersionFailedException was thrown.
Can you do a Get latest from that folder?
Is there an error in the Vault server log file that corresponds with the client-side error?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 2
- Joined: Wed Jul 20, 2005 9:30 am
I use the settings, "The current version in the repository now" and "Recursive"lbauer wrote: What diff options are you using for your folder diff: are you comparing the working folder verson to the last get; repository . . .?
lbauer wrote: Can you do a Get latest from that folder?
I'm pretty sure I can, but I didn't test it on differing versions of files.
I actaully think I figured it out.
If the 260 char length error occurs, it seems the second error will be raised for each sucessive attempt, even for different folders. The quick fix is to just restart the Vault client.
Thanks for the help, I will post more here if I have more problems concerning this.