VSS import does not import labels
Moderator: SourceGear
VSS import does not import labels
We are planning to migrate from VSS to Vault. I am just doing some tests on an evaluation version of Vault.
On testing an import of our approx. 1.5 GByte VSS database we got some exceptions "VaultServiceBase.VaultTreeException: _htFolderEntries did not contain an entry for [NAME]" (see attached file for exception messages in import tool window and the sgvault.log file) and most labels are not imported. Except for the labels the import seems to be successful.
I considered all "Tips for a successful VSS Import" except 1: The import tool, SQL server and Vault is running on the same machine.
System information:
Client Information
Vault Client Version: 4.1.1.18060
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Total Physical Memory: 2 GB
Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Server Information
Vault Server Version: 4.1.1.18060
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
SQL Version: Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
3 serial number(s):
1 of 3: 10 full users, expiring 15.05.2008
Invalid serial: ...
Invalid serial: ...
On testing an import of our approx. 1.5 GByte VSS database we got some exceptions "VaultServiceBase.VaultTreeException: _htFolderEntries did not contain an entry for [NAME]" (see attached file for exception messages in import tool window and the sgvault.log file) and most labels are not imported. Except for the labels the import seems to be successful.
I considered all "Tips for a successful VSS Import" except 1: The import tool, SQL server and Vault is running on the same machine.
System information:
Client Information
Vault Client Version: 4.1.1.18060
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Total Physical Memory: 2 GB
Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
Server Information
Vault Server Version: 4.1.1.18060
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
SQL Version: Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
License Information
3 serial number(s):
1 of 3: 10 full users, expiring 15.05.2008
Invalid serial: ...
Invalid serial: ...
- Attachments
-
- sgvault.ZIP
- (7.5 KiB) Downloaded 144 times
-
- Exceptions.ZIP
- (2.34 KiB) Downloaded 149 times
Empty folders are created !? (Importing labels continues)
Hi Beth,
thanks for the import tool debug version, my import tests are contining.
I made (see also http://support.sourcegear.com/viewtopic.php?t=6949) an export and import of our VSS database to get rid of errors, which are not reported by the "analyse" tool. During the import many error messages were displayed "File or project not found." Possibly theses error were responsible for the label import bug.
Then I started to import the project in smaller chunks without importing the labels. I change the folder structure and get empty folders (see attached screenshots). Is it safe to delete these folders?
thanks for the import tool debug version, my import tests are contining.
I made (see also http://support.sourcegear.com/viewtopic.php?t=6949) an export and import of our VSS database to get rid of errors, which are not reported by the "analyse" tool. During the import many error messages were displayed "File or project not found." Possibly theses error were responsible for the label import bug.
Then I started to import the project in smaller chunks without importing the labels. I change the folder structure and get empty folders (see attached screenshots). Is it safe to delete these folders?
- Attachments
-
- The are the files in the new folder structure
- FilesAreInNewFolderStructure.gif (18.57 KiB) Viewed 5388 times
-
- VSS' original folder structure is imported without files.
- OriginalFolderStructureFromVSS.gif (16.21 KiB) Viewed 5388 times
1. The imported projects are neither branches nor shares. I just changed the Vault target folder structure but the VSS folder structure was created in Vault additionally. But it's no problem - I will delete it after the import.
2. On running analyse I did not get errors at all, but I ran analyse with the options "-F -V3" and not with the options "-C -D -F -V4" you proposed in your mail. I will run it with these options later. Currently an import of the backuped/restored VSS DB is running for some hours and I want to wait for the results.
2. On running analyse I did not get errors at all, but I ran analyse with the options "-F -V3" and not with the options "-C -D -F -V4" you proposed in your mail. I will run it with these options later. Currently an import of the backuped/restored VSS DB is running for some hours and I want to wait for the results.
Archive / restore did not solve the problem
After archive / restore, importing in smaller chunks and importing data first and labels later the same exception occured as in the beginning (see att.).
Analyse with options "-C -D -F -V4" on the archived / restored source safe DB is currently running.
Analyse with options "-C -D -F -V4" on the archived / restored source safe DB is currently running.
- Attachments
-
- importlog.zip
- (646.5 KiB) Downloaded 141 times
> Based on the log though, it looks like the error only occurred on the label portion, correct?
Yes, thats correct. Importing the files without labels was successful and reported no errors.
I ran analyse with options "-C -D -F -V4" on the archived / restored source safe DB, which reported no errors.
I am at my wit's end. What to do now? Perhaps I can archive a smalll portion of our VSS DB which can reproduce the error and send it to you, so you can anaylse it more closely and perhaps fix it in a future Vault version.
Yes, thats correct. Importing the files without labels was successful and reported no errors.
I ran analyse with options "-C -D -F -V4" on the archived / restored source safe DB, which reported no errors.
I am at my wit's end. What to do now? Perhaps I can archive a smalll portion of our VSS DB which can reproduce the error and send it to you, so you can anaylse it more closely and perhaps fix it in a future Vault version.
Is every label needed?
In the KB article, Options for a VSS import, it suggests only importing the most important labels. If you label every build, are there builds that you aren't going to be going back to any more? If so, those might be the labels to not worry about.
In the KB article, Options for a VSS import, it suggests only importing the most important labels. If you label every build, are there builds that you aren't going to be going back to any more? If so, those might be the labels to not worry about.