Label promotion after "share, pin, and branch" operation fails

The problem occurs when you are creating a new project by using the procedure that is named "Share, Pin, and Branch to Create Service Pack Projects" (see Help). As described in the procedure, you should choose NOT to branch after share. If you do choose not to branch after share, this action sets up a new-shared project and pins all files at the version label that was selected. Then, if you try to apply a label to the new project at the project level and then branch and update one of the files, relabeling the latest revision of the branched file and doing a get on the project label returns the file at the original prepromoted labeled version.

To resolve this problem, obtain the latest service pack for Microsoft Visual SourceSafe 6.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visual SourceSafe 6.0 Service Pack 6.