Import failed, but a hidden folder seems to exist

[bpd]

After running an import recently I had a nasty error message at the end of the import to do with a missing file, and a line stating the Transaction had failed.

Sure enough after launching the Vault Client my newly imported directory wasnt there, however, I now possesed 2 of every other folder that was already in Vault - every folder at the root of my tree where I attempted my import was duplicated.

After deleting my c:\Documents and Settings\<User>\Application Data\SourceGear folder and realunching the client this corrected itself - so Im assuming the local tree structure cache was screwed?

Anyway, I then tried to re-import and was told that an item with the same name or object id already exists in the selected folder - but I cant see a folder with that name ?

Is there some way to force the Vault Client to fix its cached views, or could this be a data issue on the server that needs to be repaired - in which case are there any repair mechanisms ?

Cheers

[jeremy_sg]

You diagnosed the problem exactly right.

You may need to correct the cached repository for the admin user as well (assuming that you're importing as admin).

[bpd]

Even if I go into the Vault client in my user account I cant create a folder with that name either - same error message, so its not user specific

[jeremy_sg]

Let me restate what you're seeing to make sure tat I understand.

You now have a folder which appears empty, but when you try to add a folder to it, you get an error message saying that the object already exists?

Send me an email with your phone number, and I'll get more details from you.

[bpd]

This is roughly the chain of events;

Attempted to import > PROJECTA

After several hours, it completed but stated a problem with a .VBPROJ file which I didnt fully understand (file could not be uploaded or something)

FYI - PROJECTA consisted of 1 folder with many sub-folders, totalling several thousand file.

Loaded up Vault Client - Cant find a PROJECTA folder anywhere in the repository, so I assume the entire import has rolled back...

ReRun Import procedure - Complains that a folder called PROJECTA exists, so I call the destination _PROJECTA instead

After completion the import states that it has failed once more - This time moaning that the file its attempting to import already exists

Loaded up Vault Client - This time a _PROJECTA folder exists, and after carefult examination seems to have all the required files and sub folders

Now heres the kicker, attempt to rename _PROJECTA to PROJECTA for obvious reasons, this is when I get the message that an object by that name already exists.

So im assuming its in the Vault database somewhere, but isnt appearing in the Vault Client because its corrupt or whatever, hence my question regarding fixing the Repository.

Hope this now makes more sense

[jeremy_sg]

bpd found that the folder was in fact there, but security settings restricted him from seeing it. By using the Admin Tool to correct the securtiy rights, he was able to delete the project and rename the new one.