Search Function Not Working

Donal.Burke · Post by **Donal.Burke** » Tue Mar 21, 2006 7:49 am

Hi,

I am using Vault version 3.1.5.3546. I checked the "lock onto this folder" check box and unchecked it again, now the search function does not work.

None of the "Search By" searches work.

Any ideas as to why this is after happening.

Thanks,
Donal

lbauer · Post by **lbauer** » Tue Mar 21, 2006 4:41 pm

I wasn't able to reproduce this problem with a Vault 3.1.8 client, though we're not aware of any Search pane bugs in 3.1.5.

When you close and re-open the client, is Search still disabled?

If you lock on a folder again, does the Search work?

Donal.Burke · Post by **Donal.Burke** » Wed Mar 22, 2006 5:46 am

I have tried restarting the system, to no avail.

Perhaps I am doing something wrong or misunderstanding the system. In the attachment, you can see that some of the items in the current folder are marked "Renegade" or "Needs Merge". However, even these items aren't being recognised in the search pane despite "Any Status" being selected. Is there any way in which this is supposed to happen?

The system has had plenty of time to update, so I don't think that can be the issue. In any case, I have tried refreshing (F5) and there is no difference.

mlippert · Post by **mlippert** » Wed Mar 22, 2006 1:53 pm

I bet I know what the problem is.

Do you have a folder on the path to your selected folder cloaked?

Search doesn't seem to search in cloaked folders, which isn't the behavior I expected, and can be either a good thing or a bad thing.

I cloak folders to prevent large amounts of data I don't care about getting copied to my working folder hierarchy. However, when I search the repository, I'm usually interested in searching the the whole thing. It's a pain to have to find all of your cloaked folders, uncloak them, search, and then re-cloak them.

Mike

Donal.Burke · Post by **Donal.Burke** » Thu Mar 23, 2006 4:50 am

One of my colleague suggested deleting the cache folder for Vault under "Documents and Settings/..." and then restarting Vault. This did the trick (although it took a long time for the repository structure to refresh when I did restart).