Import creates quadrupled copies of folders

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Niklas Dahlquist

Import creates quadrupled copies of folders

Post by Niklas Dahlquist » Tue Mar 30, 2004 9:05 am

When trying to import and old VSS dbase into a sub folder in the repository.
I get several 4 copies of existing folders and first directory level from the imported VSS dbase.

How can i avoid this ?

/Niklas

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Tue Mar 30, 2004 9:14 am

This doesn't make sense to me, as Vault will not allow 2 objects to have the same name in the same folder. Could you post a screenshot to demonstrate what you're seeing?

Niklas Dahlquist

ScreenShot of quadruple folder effect

Post by Niklas Dahlquist » Wed Mar 31, 2004 4:17 am

Hi,

Here are two screen shots of my Vault tree. I tried to import /$ from VSS to folder $/TE/VSS in vault.
Error
1. Got 3 extra copies of all existing folders in vault
See folder $/MSC, Example 1

2. Got 3 extra copies of root folders in old VSS dbase
See folder $/TE/VSS/BIN, Example 2

/Niklas
Attachments
VaultScr1.JPG
Screen Example 1
VaultScr1.JPG (143.24 KiB) Viewed 7624 times
VaultScr2.JPG
Screen Example 2
VaultScr2.JPG (89.11 KiB) Viewed 7630 times

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed Mar 31, 2004 6:38 am

Do all users see the same quadrupled repository?

I think that your client side cache files might be corrupt. Try deleting them as outlined at http://support.sourcegear.com/viewtopic.php?t=6

My hope is that the server only has one copy of the folders, but your client side cache files have four. Were you logged in while the import was going? I've seen weird things happen while trying to refresh on a currently importing server.

Niklas Dahlquist

Deleting Client Cache

Post by Niklas Dahlquist » Wed Mar 31, 2004 7:34 am

I deleted all the files in:

%APPDATA%\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}\

It was a problem with the cache, deleting all the files solved the issue.

Yes, I had a client logged into vault, while executing the VSS import tool

Thanks,

Niklas

Post Reply