Pinning Problem with SourceSafe Import Tool

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

Moderator: SourceGear

Post Reply
davenovak
Posts: 222
Joined: Mon Jan 15, 2007 2:15 pm
Location: Atlanta, GA

Pinning Problem with SourceSafe Import Tool

Post by davenovak » Tue Jan 16, 2007 11:00 am

I am using the very latest Vault tools (3.5.1) and seem to be having a problem with SourceSafe imports. For reasons unknown, some files are being imported and marked as pinned to an earlier version. Therefore, when I do a "get latest", I end up getting the pinned version. Yet in the SourceSafe database, these files are not pinned.

The only thing I can see that makes these files different is that they were currently checked out in the SourceSafe yet newer versions were checked in on top of these.

Here are my steps to reproduce the problem:
  • 1. Using an existing archive, check out a file as user1
    2. As user2, check out the same file and make a change to that file and check it back in.
    3. As user2, again make another change to that file and check it back in.
    4. Note that user1 still has the file checked out, though more recent changes have been checked in
    5. Make an archive backup of this SourceSafe database.
    6. Create a new SourceSafe database and restore this backup.
    7. Note that in the new SourceSafe database, this file is neither checked out or pinned.
    8. Use Vault SourceSafe Import Tool to import this database.
    9. Using the Vault client, this file is pinned in the new Vault database.
Unfortunately, I have already found out that there is no easy way to search for pinned files in order to unpin them (http://support.sourcegear.com/viewtopic.php?t=7273).

Any suggestions for a workaround?

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

Post by lbauer » Tue Jan 16, 2007 3:05 pm

Pins are tricky to detect on import, since we have to go through the entire history and track pin/unpin, pin/unpin, etc. and hopefully end up in the right state. Pins are applied at the very end of the import.

It's possible something about the "multiple checkout plus file has changed state" is making the import think the item has been pinned. I'll log a bug and we'll try to reproduce this.

We're also looking to see if we have a tool for unpinning files that may help you.
Linda Bauer
SourceGear
Technical Support Manager

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Tue Jan 16, 2007 4:55 pm

Can you send an email to support at sourcegear.com and reference this post? I think I may have something you can try out.

davenovak
Posts: 222
Joined: Mon Jan 15, 2007 2:15 pm
Location: Atlanta, GA

Post by davenovak » Thu Jan 18, 2007 2:04 pm

I tried both the pinning and unpinning PowerToys and they work! Thanks! That will save me a lot of time. :D

Post Reply