No object can have the same label applied twice?

[luther_miller]

When doing an import, I was prompted which labels I would like to import. I selected them all, of course; each label refers to a build that went to stage or production. Then Vault told me that "In Vault, no object can have the same label applied twice." What does this mean and what are the implications?

[luther_miller]

Ok, the import didn't take the estimated 1 day, but only a few hours. However, there were many errors:

I got two of these that don't make any sense to me:
Item $/Softagon caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed
Item $/Softagon caused the transaction to fail: An item with the same name or object id already exists in the selected folder.
Transaction failed

I got a TON of these - probably hundreds maybe thousands:
**Failed** to Get version [some number] of [some file] to upload.

And I got a whole slew od these:
Label Import: The label $/ (2.2.0110) could not be imported because an exception occured.


A couple of notes:
1) The VSS database has no errors or warnings when using analyze etc - in fact, we have never had any problems like that, and this database has been in use for 2 years
2) The VSS database is 6.0d
3) The VSS database was once archived and restored many many months ago
4) We have been using SOS 3.5 with the VSS database for 2 years

I have access to a couple of hotfixes related to VSS 6.0d that I have not install on the computer where I ran the Import utility, so maybe I will try that. The VSS database is on another machine. Vault and the import utility were just freshly installed on a freshly installed Windows 2003 Server with SQL Server 2000 and VSS 6.0d.

Am I going to be able to import this project sucessfully? Whether or not we buy Vault to replace VSS or we simply add a couple more licenses of SOS 3.5 rides on this...
Thanks!
-Luther

[GregM]

Have you read the Tips for a successful VSS Import document at the top of this forum?

http://support.sourcegear.com/viewtopic.php?t=8

3. On the machine with the VSS database, you should be running SourceSafe 6.0c, plus the following hotfix from Microsoft:

http://support.microsoft.com/default.as ... us;Q323917

The hotfix is also available at

http://www.sourcegear.com/vault/downloa ... hotfix.zip

Do not use SourceSafe 6.0d.