Client Remote Version does not match Local (v3.0, 2.06)

roman · Post by **roman** » Tue Dec 07, 2004 10:41 am

Two of our developers see a Remote Version of the file by one ore two behind. For example for one of them: Remote Version 469 shows in the client , but when he go and see Vault file history, there is version 470. When he gets the latest version, it gets the version 469. He can 'Get' v470 from file history, but then the Vault Client says that the Local Version is 470, but Remote Version is 469 and client does not seem happy about it. The next Get Latest Version brings back v469!!!

It happened on one of my PCs in the past also. Happened on 2.06 in the past and continues in 3.0.

I believe this is a very serious problem. Is it a known bug? If not, do you need our help to track it down?

Post by **jeremy_sg** » Tue Dec 07, 2004 11:14 am

It sounds like you are seeing a pinned file. If you right click on the file, you should be able to unpin the file. If that is not the case, please respond so that we can track this down.

Post by **jclausius** » Tue Dec 07, 2004 11:16 am

One other idea to check, if the file (or parent folder) is not pinned...

Is it possible someone restored or changed one of the client side cache files for that particular user that the Vault client somehow got of of sync?

You could check this out by:
1) Closing all instances of Vault ( IDE and GUI ) clients on the user's machine.
2) Delete the Cache_Repository file in the user's %APPDATA%\SourceGear\Vault_1\Client\{RepID}\ folder. See Vault Client-Side Cache Files regarding more information regarding this file.

Guest · Post by **Guest** » Tue Dec 07, 2004 12:21 pm

jclausius, the file is not pinned. Also, I did the procedures that you recommended in the past, and it helped, but the problem came back after a few weeks (for the same user).

Post by **jclausius** » Tue Dec 07, 2004 12:51 pm

Is there anything you can tell me about the user and your setup for %APPDATA%?

Is it possible this directory exists on a network drive?

Anything that would suggest the file is modified outside of Vault?

Do you use folder security? Has security been toggled on the folder path?

Any information you can provide would be helpful.