Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
TeamSite Search Java IO Error
eehall
I currently have Search 2.1 installed, but I am experiencing a permissions related error that has me stumped.
When a user executes a query from the UI they receive and error.
The error in the iw.tssearch.log file looks like this:
## ERROR MESSAGE INCLUDED BELOW ##
ERROR com.interwoven.hunter.search.QueryProcessor (Thread-7) - Error generating query ID
java.io.IOException: Permission denied
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:850)
at com.interwoven.hunter.search.QueryProcessor.generateInternalID(QueryProcessor.java:658)
at com.interwoven.hunter.search.TeamSiteQueryProcessor.doQuery(TeamSiteQueryProcessor.java:93)
at com.interwoven.hunter.search.commands.QueryCommand.execute(QueryCommand.java:163)
at com.interwoven.hunter.search.SearchWorker.run(SearchWorker.java:88)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
ERROR com.interwoven.hunter.search.SearchServer (Thread-7) - com.interwoven.hunter.search.QueryProcessingException:
Error generating query ID
## END ERROR MESSAGE ##
Any idea where TeamSite is trying to create this ID so that the permissions can be fixed?
Find more posts tagged with
Comments
Migrateduser
Please post the details of your Platform (Solaris ?) and the installation order.
Also the details of the persmissions of some folders in Search_home/temp.
--hemant
Migrateduser
You can get it working by changing the permissions on the directory and files, but this should not be happening in the normal course.
eehall
I'm on Solaris.
However, I deleted the entire contents of our TS Search installation directory (following an unistall of TS Search) and then reinstalled the application. This resolved the issue. I am unsure which file or directory was causing the problem, but we got it working with the slash and burn approach.
Thanks.
Migrateduser
This must have been the upgrade case which messed up with the non-os user. Will take note of this. BTW did you rebuild the indexes or use the old ones ?