VSS Import

** Re-posted without logfile attachment (if some from SourceGear would
like to see the log file please let me know).
 
I have just imported a simple VSS database and got the following errors:
 
**Failed** to Get version 1 of $/Test/Test 2/TextPin.txt to upload.
**Failed** to Get version 2 of $/Test/Test 2/TextPin.txt to upload.
**Failed** to Get version 3 of $/Test/Test 2/TextPin.txt to upload.
**Failed** to Get version 4 of $/Test/Test 2/TextPin.txt to upload.
**Failed** to Get version 5 of $/Test/Test 2/TextPin.txt to upload.
**Failed** to Get version 1 of $/Test/TextPin.txt to upload.
**Failed** to Get version 2 of $/Test/TextPin.txt to upload.
**Failed** to Get version 3 of $/Test/TextPin.txt to upload.
**Failed** to Get version 4 of $/Test/TextPin.txt to upload.
**Failed** to Get version 5 of $/Test/TextPin.txt to upload.
Label Import:  The label $/Paxton/Net2/Communications Server (0.00.007)
could not be verified because an exception occured.
Label Import:  The label $/Paxton/Net2/Communications Server (0.09.026)
could not be verified because an exception occured.
The label $/Paxton/Net2 (V0.17 Beta 2) was renamed to V0.17 Beta 2
vssimport 2.
The label $/Paxton/MagCard (V1.00.002) was renamed to V1.00.002
vssimport 2.
00:20:16.1923646
 
1. I understand the **Failed** errors because these 2 files have the
source-safe option "Store only latest version" set. In this case it
might be nice if the import actually ignored these errors (or told you
the reason) but also stored the file in Vault with the current version
number.
 
2. I don't understand the "Label Import" errors. I have attached my
import log file if that help. (I followed all the instructions at
http://support.sourcegear.com/viewtopic.php?t=8 before starting the
import.)
 
3. This would be a fairly rare bug but I used the Admin tool to delete
my first attempt at importing VSS. When I ran the import again there was
an exception when it got to the "select repository" step, presumably
because there wasn't a database. I selected continue and just created a
new DB and the import continue smoothly.
 
4. At the end of the import log there is the following:
    Begin Export - Pins....
 
    Pinned $/Test/TextPin.txt to version 3 ($/Test/TextPin.txt) at
21/06/2000 20:02:44
    **Failed** history query for pinned item's id. Unable to pin
$/Test/TextPin.txt to version 3
    VaultLib.VaultSoapException: 1010 :  FailInvalidRange 
       at VaultService.VaultService.GetHistoryQueryItems(String
strQryToken, Int32 nStart, Int32 nEnd, VaultHistoryItem[]&     vhiItems)
 
Does this mean that no PINs were imported or is this just another
problem with the "Store only latest version" setting of this file?
 
 
 
Despite these issues Vault looks much better than when I last looked at
an early V1. I like the new support for "proper" labels!
 
Neil
 
Neil Sleightholm
X2 Systems Limited
neil@xxxxxxxxxxxxx

<<winmail.dat>>