all files pinned after import

[ww]

I've imported a very large VSS project in which we used share/pin/branch to track two branches of a product. After the import, every single file in the variant line is pinned, regardless of whether they're even shared any more.

For example, a file was shared, pinned, and then branched in VSS. In Vault it's not shared (which is correct), but it is pinned, which it shouldn't be.

I can use the API to clean up the mess by unpinning all files that aren't shared, but I'd like to know why this happened so I can avoid it on the next import.

[lbauer]

It's difficult for us to determine a file's pin status during the import. (We communicate with the VSS database via the SourceSafe Automation Component.)

We look for an odd number of pin/unpin requests and sometimes the Import Tool gets it wrong.

We haven't had many reports of pinned files that shouldn't be pinned. It's possible reimporting will give you different results, or that you'd get different results on a different database. The fix is to unpin the files manually, as you've done.

However, the pin is applied at the end of the import process, so that all files and versions should be retrieved correctly, which is our first priority.