Incomplete Import

suheil · Post by **suheil** » Mon Jun 12, 2006 1:05 pm

Hi

I am trying to import a VSS database into Vault. When the Import tool finishes, I have 37 errors, telling me that various versions of various files could not be imported, e.g.
**Failed** to Get version 4 of $/TTSigScripts/DAASig/padStart.frx to upload.

1) What could be causing this, and is there a way to get over it?

2) I noticed that the Import Tips (http://support.sourcegear.com/viewtopic.php?t=7) advise not to use VSS 8.0d. I checked my VSS version, and found that it is in fact 8.0d. Is this a major problem, and if so, how can I change it to 8.0c?

Thanks,

suheil · Post by **suheil** » Mon Jun 12, 2006 2:31 pm

PS: I do have a Temp directory as a sibling to the srcsafe.ini file on the VSS server.
Thanks,
-s

lbauer · Post by **lbauer** » Mon Jun 12, 2006 3:08 pm

Are you using VSS 6.0d or VSS 2005 (VSS 8.0)? We don't recommend VSS 6.0d. If you're using VSS 6.0d, download the 6.0c Hotfix from this KB article and use that instead.

http://support.sourcegear.com/viewtopic.php?t=7

Or you can use VSS 2005 (VSS 8.0). As far as we know, there's no VSS 8.0d, just 8.0, and VSS 8.0 seems to work for imports.

Lack of a temp directory can cause the error message you're seeing, but generally NO files are imported. Is that what you are seeing? Or are you getting this failure just on some files?

Is there a limit on space for that Temp directory?

Have you run Analyze on your VSS database, using the -f and -c parameters? This is an important step, since the VSS automation component is very sensitive to minor database corruption. The Vault Import Tool uses the VSS automation component to communicate with the VSS database.

suheil · Post by **suheil** » Tue Jun 13, 2006 9:49 am

- I'm using VSS 6.0d (not 8.0d, sorry). I shall download the fix to downgrade it to 6.0c.

- It is only certain versions of certain files that are failing. Most of the history has been imported without giving errors.

Thank you,
-s[/quote]

suheil · Post by **suheil** » Tue Jun 13, 2006 11:16 am

- I ran analyze -f -c. It said some errors had been found anf fixed. But when I tried the import again after this, I still got the same errors.

- I downloaded the HotFix zip file from the sourcegear link in the page you referred me to. It contains about 25 files (most of which look like they belong in the vss\win32 folder on the server) plus a hotfix folder with ssexp.exe and ssadmin.exe files. I'm not sure how exactly I am supposed to go about applying this patch to my VSS 6.0c. I tried replacing the ssexp.exe on my client and running the version extracted from hotfix, but it gives an error even before coming up. Can you please tell me how to go about this?

Thanks,
-s

lbauer · Post by **lbauer** » Tue Jun 13, 2006 4:27 pm

These are the instructions in the Hotfix.txt file:
1. Make a backup copy of your \vss\win32 directory
2. Copy the extracted files into the \vss\win32 directory

I'm not sure why there's an additional Hotfix directory with extra clients in it. This is the way Microsoft originally provided the fix. The important file is the ssapi.dll, the VSS automation component. The Import Tool communicates with the database through the automation component. The version of the ssapi.dll file in the hotfix is 6.0.96.4.