We are running Vault 4.1.1 (18060), and over Memorial Day weekend attempted to import our main VSS database over to Vault. It is over 6 GB in size. The import ended with 23,000+ errors. I can send the entire error log via email (it is 2.7 MB). I am attaching a subset of the error log.
Can you tell me what is causing the various failures? Why are the exceptions happening?
After the import ended, most of the subdirectories were there, but several were completely missing.
We started with a clean VSS database, on which we ran Analyze with the following command line:
"C:\Program Files\Microsoft Visual SourceSafe\analyze.exe" -F -C -V4 -S "D:\Latitude\Source\data"
[/b][/u][/i]
VSS to Vault import errors
Moderator: SourceGear
VSS to Vault import errors
- Attachments
-
- VaultImportErrors20080525Subset.txt
- Subset of errors (25,000+ lines in the original error log).
- (73.02 KiB) Downloaded 202 times
=====================
David West
PathGuide Technologies, Inc.
David West
PathGuide Technologies, Inc.
Importing is a very large task. You will want to make sure you familiarize yourself with the following articles before beginning.
Tips for a Successful VSS Import
Options for a VSS Import
Can you tell me the version of the VSS automation component you are using? Instructions for finding that are here: Automation Component Version
If possible, I would suggest starting with a fresh repository, or create a test repository to try a few things out on first. It's easiest to delete repositories with no ill effect.
Tips for a Successful VSS Import
Options for a VSS Import
Can you tell me the version of the VSS automation component you are using? Instructions for finding that are here: Automation Component Version
If possible, I would suggest starting with a fresh repository, or create a test repository to try a few things out on first. It's easiest to delete repositories with no ill effect.