Moving client to new machine, lost pending change set

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
kkchan
Posts: 54
Joined: Wed Jun 30, 2010 12:45 am

Moving client to new machine, lost pending change set

Post by kkchan » Wed Mar 13, 2013 7:43 pm

Hi
I am moving my Vault Client to to new machine.
I have copied all my source file, and local cache folder to new machine as well (same location as old machine).
All the settings are retained, but the pending change set is lost.

Edited: beside, all the checked out files status become "Renegade" instead of "Checked Out"

How to resolve it?

Thank you

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Moving client to new machine, lost pending change set

Post by lbauer » Wed Mar 13, 2013 11:17 pm

Vault client keeps track of the machine where the checkouts are made. If the client is on a different machine, Vault client sees the files are checked out, but not on the new machine. The pending change set is gone because there are no checkouts on this machine.

Probably the best way to resolve it is to checkout the files on the new machine, making sure you use the "don't overwrite, merge later option." At some point, you would need to undo the checkout, using the "leave" option, so the file won't revert back to the repository version.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply