VSS Import fails... lost VSS connection?

[mepstein]

We are demo'ing the Vault product and twice I have unsuccessfully tried to import our VSS database. It hangs up on the same file each time and pops up an error message in a message box: Object reference not set to an instance of an object.

I looked at the logs and it shows this:
Refreshing SourceSafe connection...
Opening: H:\vss\srcsafe.ini
User: admin
VSS database open: False

9/20/2004 1:09:39 AM - Refreshing connection to the Vault server.

Logged out of the Vault Server.
Connected to Vault.
Checked in $/XXXXX/YYYYY/Build ($/XXXXX/YYYYY/Build/build readme.txt) at 5/6/2003 4:55:46 PM(Links: $/XXXXX/Branches/ZZZZZ/Build/build readme.txt )
Change set type: Modified
**Failed** to get the VSSItem for version 1015 of: '$/XXXXX/YYYYY/Build/build readme.txt'
System.NullReferenceException
Object reference not set to an instance of an object.

After this point in the log, everything is toast.

I looked around the other posts and didn't see this exact problem, but I'm not the expert.

FYI: This file occurs relatively early in the overall import progress. The VSS data store is a little over 2 GB so I guess the file scan prior to import could have already sucked up a lot of memory -- the server only has 512 MB of physical RAM.

I didn't think to check the memory usage when I killed the import, so that's my mistake. But this is our production server so I'd rather not re-run it (or backup the VSS store to test it off that) if I don't *have* to -- at least not right now.

Any advice?

TIA,
Matt

[jeremy_sg]

Matt,

Email me using the button below and I will send you a new build of the import to try. The new build uses less memory and should be better about logging errors.

-Jeremy