VSS Import Errors

I posted a long rant last night which never made an appearance on the
list cos it exceeded the 60K limit.....
 
Anyway, after 9 hours processing last night, I can happily say that
everything failed to import, so I was left with an empty Vault
repository and nine hours of my life I'll never get back....
 
But having trolled the log file (can you keep display and error/success
count on the VSS import form? Would have saved me a lot of time last
night) that the importer creates, there is the same error over an over
again... :
 
Beginning Export.
Begin Export....
 
Memory used: 35872768.
Created  ($/Redgum/Testing) at 4/2/2001 1:30:10 PM
Change set type: CreateFolder
Adding to transaction: $/Redgum/Testing - $/Testing
Server unavailable for transaction end
Transaction failed
Transaction failed
**Failed** - Error trying to commit. Exception of type System.Exception
was thrown.
Trace:   at VSSImport.WizardForm.a(String A_0, DateTime A_1, Int32 A_2)
12/17/2003 10:18:47 AM - Unable to commit for 4/2/2001 1:30:10 PM -
$/Redgum/Testing - Created .
Refreshing SourceSafe connection...
Opening: D:\SourceSafeData\Redgum\srcsafe.ini
User: admin
VSS database open: True
 
12/17/2003 10:18:47 AM - Refreshing connection to the Vault server.
 
Logged out of the Vault Server.
Connected to Vault.
Server unavailable for transaction end
Transaction failed
Transaction failed
**Failed** - Error trying to commit. Exception of type System.Exception
was thrown.
Trace:   at VSSImport.WizardForm.a(String A_0, DateTime A_1, Int32 A_2)
12/17/2003 10:19:18 AM - Unable to commit for 4/2/2001 1:30:10 PM -
$/Redgum/Testing - Created .
Refreshing SourceSafe connection...
Opening: D:\SourceSafeData\Redgum\srcsafe.ini
User: admin
VSS database open: True
 
 
etc, etc......
 
Vault itself seems to be running OK - the Client and Admin tools both
connect OK... the SQL database is online and accessible. 
 
The machine being used for the upsize is a 1.1Ghz Celeron, 1Gb RAM,
Windows 2K fully serviced packed and freshly built from scratch
yesterday. Only applications installed on the machine are VB6
Enterprise, VSS 6.0c, Vault Server, Vault Client and Vault VSS Import
Tool, SQL Server. Destination database is MSDE SP3, again freshly
installed yesterday. Only database attached (apart from the default 4)
is the Vault DB. Everything else is local, VSS Database, IIS, SQL
Server, the works. 
 
I'm using the SUE edition (for the import only - once I'm happy with the
import, I'll roll out the dev licences I need), so I don't know if the
problems are related to the restricted user count - there are about 10
users (past and present in the VSS database, of which 5 were active in
the VSS project branch I'm importing) or what.
 
Any ideas?
 
Matt
 
____________________________________________
Matt White
Software Engineer  <mailto:[email protected]>
[email protected] Advanced Publishing Systems Pty Ltd
Phone: (03) 9940 1441 Fax: (03) 9940 1458 
	
420 Victoria Street
Brunswick VIC 3056