Re: VSS Import

Neil,

You are right as to the cause of the TextPin.txt failures, if VSS 
doesn't have those versions, then we can't import them.  I'm working 
with another customer on tracking down the "exception occured" failure 
for some labels.  If you would like to help me track this down for you, 
email me offlist and we will get it figured out.  As for the pin of the 
file that is missing a version, your diagnosis was right.  Did the other 
pins in you database get imported? 

Thanks for the import feedback. 

-Jeremy Sheeley



Neil Sleightholm wrote:

>** 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
>[email protected]
> 
>  
>
>------------------------------------------------------------------------
>
>****
>NOTE:  An attachment was deleted from this part of the message,
>because it failed one or more checks by the virus scanning system.
>The file has been quarantined on the mail server, with the following
>file name:
>
>	att-winmail.dat-40123e70.NQ
>
>The removed attachment's original name was:
>
>	winmail.dat
>
>It is recommended that you contact your system administrator if you
>need access to the file.  It might also be a good idea to contact the
>sender, and warn them that their system may be infected.
>****
>
>------------------------------------------------------------------------
>
>This message has been 'sanitized'.  This means that potentially
>dangerous content has been rewritten or removed.  The following
>log describes which actions were taken.
>
>Sanitizer (start="1074937455"):
>  Part (pos="2274"):
>    SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
>      Match (rule="2"):
>        Enforced policy: accept
>
>  Part (pos="5333"):
>    SanitizeFile (filename="winmail.dat", mimetype="application/ms-tnef"):
>      Match (rule="1"):
>        Enforced policy: save
>
>      Replaced mime type with: text/plain
>      Replaced file name with: DEFANGED-161.txt
>
>  Total modifications so far: 1
>
>
>Anomy 0.0.0 : Sanitizer.pm
>$Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $
>  
>