Repository shows "no files" once it is mapped to a folder

[peterbrown05]

Hello
We have a number of repositories in our vault db...

We have recently started to see that for some users on some repositories that once a respository is mapped to a working folder, then the folder structure of the repository remains but any files within those folders are "invisible".
If the folder is NOT mapped then the files are visible.

This makes working with vault impossible.

We have tried completely clearing/deleting the vault cache but the problem persists.

One developer tried the same thing on his laptop machine and it worked ok; but on his desktop machine it did not.

Can you help explain what we need to do in order to fix this?

fyi we are running Vault 5.0.3.18802

please advise urgently as this is stopping us from working!

kind regards

peter brown

[lbauer]

Could you post a screen shot of what you're seeing (or not seeing?)

[peterbrown05]

2 images attached; 1 showing it "working" where on a different machine the same user is logged in and can see the files and the vault status (missing, renegade etc)

and the other where the same user on a different machine cant see any files at all.

cheers
peteB

[peterbrown05]

..ok ; ive just tried again on one of our build boxes. nuked the vault cache. started up vault, opened this repository,
--> files show with status of Unknown

set working folder

--> no files visible.

[lbauer]

I'd suggest we schedule a remote assist session where I can take a closer look. Email support at sourcegear.com, Attn: Linda, and we'll set something up. Please include a link to this forum post.

[peterbrown05]

ok thanks
i have sent the request email

[lbauer]

We did find another case similar to yours. That case involved "ghosted" files and folders.

Do your users have "ghosting" turned on? This setting is in the Vault Client under Tools->Options->General->Show non-version-controlled files ghosted in the file list.

If so, disable that setting and see if it make a difference.

[peterbrown05]

It seems that once we turn "“Show non-version-controlled files ghosted in file list” off then the files are visible again.

We will keep monitoring the situation and let you know if we have further problems.

Is this issue resolved in the latest version of Vault?

[lbauer]

We were never able to reproduce the problem. We think it's something to do with the user's database/repository, but have not been able to get a copy of a database that is experiencing the issue.

Would you be interested in sending us a copy of your database for testing?