Vault 2014 Search not functioning

[richardp]

Hi all,

Recently, just out of the blue (apparently) our vault (basic) clients seem unable to search for files. We can manually locate the files but as soon as we try to search for them, vault returns with 0 results and displays the generic message 'There are no items to show in this view.' Even if I am in the folder where the file is located, vault cannot find the file I am requesting.

We've updated to Service Pack 2, downgraded to .Net 4.0 and still no joy.

If anyone has a solution, please advise.

Attached are screenshots of the file search fail.

[paul.gunn · Accepted solution]

Hi Richard,

I would suggest rebuilding the search indexes. This can be done via ADMS console on the server. It is possible that the existing indexes have become damaged or corrupted in some way .

Paul

[johannes.bauer]

Hi Richard,

here you can see a KB Article who shows how this is done.

[richardp]

Gentlemen,

Thank you very much for your assistance. We are back on track!

Much appreciated!

RP

[eric.gauthier]

Hi Paul,
Do you know if your solution can resolve my problem which is that file containing a "dot" in its filename (like '782.0167.ipt') doesn't display in a search results? I'm using Vault Basic 2014.
Thanks,

[paul.gunn]

Hi Eric,

If you are finding other similar files, but not this one in particular, then (yes) an index rebuild may be helpful. Another thing to try might be an advanced search with the 'is' operator. The default 'contains' search does tokenization on characters like '.' - which 'is' searches will not do. Even with the default search though, I would expect your search to return the desired results (if anything the default search might return more results than expected) .

Paul

[eric.gauthier]

Hi Paul,

I can keep my search to 'contains' but I have to add an '*' in place of the '.' which means to get my '782.0167.ipt' file, I have to search for '782*', just searching for '782' does NOT return my file. A 'contains' search with '782.0167' will find my file but searching '782.0' will NOT. Personally, I would expect a 'contains' search to work with '782.0'...

Thank you for your quick answer!

[paul.gunn]

Hi Eric,

It seems like other delimiters like '-' are treated differently than '.' . e.g. if I add a file with the name 782-0167 to vault then the search for 782 will find the file. I'm not sure why the two characters are treated differently in Vault and whether this was intentional - this behavior goes back over 10 years now.

I can say that searching for '782.0' or '782-0' will never work without the wildcard and is not intended to. If we automatically did partial number searches, one could potentially get excessive numbers of results - which many customers would dislike. The wildcard allows access to those expanded numbers of results but is needed explicitly  to 'opt in' to that behavior.

Paul