VSSImport0 files after Source Safe import

mballou · Post by **mballou** » Wed Oct 12, 2005 10:47 am

I have successfully imported a fairly large amount of files from Source Safe into a new repository in Vault. Everything is working fine except for two issues. I'm used Vault 3.1.2 to import and for the admin tool.

1. When I go into the Obliterate tab for the repository there are thousands of files that end with VSSImport0. It looks like there is one for every version of every file that was in the original source safe folder. It takes a very long time for the list view to populate (over 30 minutes at least). I went home last night after the list view started to fill up. This morning when I try to select them and hit the obliterate button, I get the following error:

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at VaultService.VaultService.BeginTx(Int32 nRepID, String strComment, VaultRequestItem[]& requests, String& strTxID)
--- End of inner exception stack trace ---

2. In the admin tool, when I click the Repositories tab, and select a repository with quite a few files and click the Properties button, SQL Server uses 100% CPU and eventually times out. I can never view the properties (and thus repository security access) when there are lots of files.

Thanks,
Mike Ballou

ian_sg · Post by **ian_sg** » Wed Oct 12, 2005 3:44 pm

The VSS import imports lots of temporary data in order to preserve the labels. If you have a large number of labels in SourceSafe, and you import them all, there will be a large number of deleted items when you're done. It sounds like you have a very large number of these.

The behavior of the obliterate tab when there is a very large number of deleted items is a bug, but in this case obliterating these deleted items would effectively break the imported labels, so that's not really an option.

Is this a new Vault install? My suggestion would be to re-install the server (getting a fresh database) and redo the import, taking care only to import labels that are important.

There are more tips for a successful VSS import here: http://support.sourcegear.com/viewtopic.php?t=8

mballou · Post by **mballou** » Fri Oct 14, 2005 1:11 pm

I imported a couple other Source Safe databases using 3.0 versions of Vault. I didn't have that issue before, so I just went ahead and imported all the labels not thinking it would be a big issue.

Unfortunately development has already started on the database so I can't redo the import at this time.

It's my fault for not reading the documentation better.

I know there is already an open bug report regarding the slow population of the obliterate dialog.
Can you make sure there is an issue opened regarding the inability to view repository properties? At this time, I am unable to adjust the security of who can access the repository.

Thanks,
Mike Ballou