Skip to main content
Inspiring
Dec 16, 2011 8:50 PM UTC
Question

Searching WebHelp Pro sometimes fails to find terms that are there

I've seen postings about this before, but we're seeing searches fail with the message "Sorry, we were unable to find a good answer for your question." even though the term being searched is present in countless places within the help.

To address this we have increased the java heap space, as advocated elsewhere and we are seeing the same intermittent problem. Digging into this further we've examined the SQL server logs and according to one of our engineers it appears that RoboHelp is occassionally passing invalid syntax as part of its search query, which causes the search engine (Lucene, I guess) to throw the error.

The pattern seems to be that a particular term or two will produce the "Sorry..." message for a week or so then another term or two will exhibit the problem and the original terms will work properly.

Here's another puzzing detail: if I right-click the body of the WebHelp Pro help page and cut the URL from the Properties dialog and then paste the same URL into a different browser page, log in past the Admin page, and perform the same search, then the search works fine.

Has anyone experienced this sort of behavior? Any ideas what might be going on?

This topic is closed to new replies. Start a new post to keep the conversation going.

15 replies

Inspiring
Jan 3, 2012 7:23 PM UTC

It's funny about the "reindex at server setting." We have three or four terms that fail the search in a predictable fashion: changing this setting from On to Off alters which of the group fails or succeeds when searching. For example, "On," results in terms A and B failing but C and D work whereas "Off" results in C and D failing but A and B work. This is repeatable.

Thanks for your help. I hope they find something in the logs.

Translate
johndaigle
Legend
Jan 3, 2012 8:29 PM UTC

Hi, Rocky. The Adobe engineers that I wanted to review your logs are returning from an extended holiday break. I will have an opportunity this week to raise this issue now that they are back.

Thanks

john

Translate
John DaigleAdobe Certified RoboHelp and Captivate InstructorNewport, Oregon
johndaigle
Legend
Jan 11, 2012 8:40 PM UTC

As a follow up to folks following this thread: Adobe engineers identified Rocky's problem after looking at his server log files and it was successfully resolved. If anyone encounters a similar problem, post it here on the forum and we'll see if we can help.

John Daigle

Adobe Certified RoboHelp and Captivate Instructor

Evergreen, Colorado

www.showmethedemo.com

Translate
John DaigleAdobe Certified RoboHelp and Captivate InstructorNewport, Oregon
johndaigle
Legend
Dec 18, 2011 2:08 AM UTC

Hi, Rocky

Can you verify that in the Configuration Manager application (which is on the server machine) is set to "Reindex Documents at Server" is checked?

If you could zip up the Tomcat log file that would be helpful.

You'll find it on this path on the Server machine:

C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0\logs\robohelpserver.log

Send it to my email which you can find in my profile at right. I'll send that to an Adobe engineer and see if we can diagnose this.

BTW, did you finally get the issue resolved mentioned in this thread?

http://forums.adobe.com/message/4014314#4014314

Thanks

John Daigle

Adobe Certified RoboHelp and Captivate Instructor

Evergreen, Colorado

www.showmethedemo.com

Translate
John DaigleAdobe Certified RoboHelp and Captivate InstructorNewport, Oregon
Inspiring
Dec 18, 2011 2:52 PM UTC

Thank you! When I return to the office tomorrow I'll investigate whether or not this etting is enabled and also pull the log files.

As for the other thread, we worked around the issue by resurrecting the virtual machine image that contained our trial install, which had been working fine, and activated the expired trial install with our newly purchased license. For whatever reason, this seemed to work fine.

Translate