Skip to main content
Mr__Flibble
Known Participant
August 25, 2015
Answered

RH 2015: WebHelp search showing 100% completion, but no results

  • August 25, 2015
  • 1 reply
  • 763 views

Using RoboHelp 2015 (12.0.1.338), and seeing this issue in both IE and Chrome. When I generate and view my WebHelp output locally, its Search feature works fine. However, when it's checked into Microsoft Visual Studio (TFS) and then deployed to a website, the Search feature might work once or twice, but on the 2nd or 3rd search, the search progress bar shows 100%, but no results appear and the page crashes.

Seems similar to the issue reported for RH9 in the discussion linked below, but I'm using a much later version of RH, and I'm not sure the RH9 fix applies. Anyone know what's going on?

Problem with latest Security Update

This topic has been closed for replies.
Correct answer Ankit Rajpoot

Ah,

Seems like WebHelp output was not copied to the web server completely.

File topictable_12_xml.js contains part of the search database.

Since the output works fine locally, this indicates some issue with server upload.

You could just try to upload "topictable_12_xml.js" to the server at location "[1st chunk of URL]/WebHelp/whxdata/topictable_12_xml.js" and see if it succeeds.

Regards,

Ankit

1 reply

Ankit Rajpoot
Adobe Employee
Adobe Employee
August 26, 2015

Hello,

Do you see any error in Chrome console when the search gets stuck at 100%.

To check, initiate a search and then open the console by pressing Ctrl + Shift + J (Windows) or Cmd + Option + J (Mac).

Errors would be listed in red in the console.

Mr__Flibble
Known Participant
August 26, 2015

Hi Ankit,

Thanks for the reply. Yes, the Chrome console is showing the following:

________________________________________________________________________

[1st chunk of URL]/WebHelp/whxdata/topictable_12_xml.js

Failed to load resource: the server responded with a status of 404 (Not Found)

Uncaught TypeError: Cannot read property 'toUpperCase' of undefined          whutils.js:149

________________________________________________________________________

Ankit Rajpoot
Adobe Employee
Ankit RajpootCorrect answer
Adobe Employee
August 27, 2015

Ah,

Seems like WebHelp output was not copied to the web server completely.

File topictable_12_xml.js contains part of the search database.

Since the output works fine locally, this indicates some issue with server upload.

You could just try to upload "topictable_12_xml.js" to the server at location "[1st chunk of URL]/WebHelp/whxdata/topictable_12_xml.js" and see if it succeeds.

Regards,

Ankit