With respect to UCF timeout issues, try disabling ACS on the Content Server.
Sure - the procedure is download the content server admin guide and then look for "how to disable ACS"
whatever version you are using
Why are you asking us to guess which version you are using? You should know which version of Content Server. If you log into DA, it will show you version:
Then you should download content server 6.7
ACS servlet runs on the Content Server. Clients using UCF, call ACS by default, to improve performance. This default behavior works fine if your ACS is running. If it isn't running, then UCF timesout b/c its waiting for response from ACS. Hence, disabling the ACS feature on the client eliminates the check. This typically fixes UCF problems if you already have the supported JRE installed for your client version.
FYI - adding her consumer/contributor role has NO impact on searching, since roles impacts UI, not security. I have stated this numerous times in your other posts.
Also, why are you talking about searching and not getting results when you original posting has to do with getting UCF timeouts? In order to trigger UCF to transfer object, you would have had to have at least READ permissions. It is bad etiquette to change topic of the discussion then what was originally posted. Create another post if you have another question.
JRE version has to with browser, not the Content Server or App Server. UCF is applet that runs on the browser to handle content transfer. If JRE on the client machine is newer than whats listed in release notes for that browser for Webtop 6.7, it may not work as expected.
you can disable the acs read and write from wdk/app.xml file to resolve the timeout error, only if the client browser has not access to your ACS server (the url can be find from your dm_acs_config object dump)