Skip to main content
Inspiring
June 29, 2022
Question

RoboHelp 2017 Webhelp search function not working

  • June 29, 2022
  • 5 replies
  • 215 views

I'm using RoboHelp 2017 and compiling/publishing Webhelp. The search function returns: Error: Failed to initialize database. Entering any query results with Null. I've seen posts related to this issue going back several years. The consensus of late is that this is related to issues with the *.js files located in the whxdata folder. The search function used to work. The issue just "happened" one day. I got an email from a user that the search function wasn't working. I checked and sure enough... no joy.

If I use RoboHelp 2017 to create a new project and generate a new Webhelp the search funtion works just fine.

Is there a way to replace/fix the missing/corrupted .js files (assuming that's the issue). I've spend time in the forum posts. In all the posts that I've read there isn't a solution for Webhelp. I've read solutions for Responsive HTML5, but I haven't found a solution for RoboHelp 2017 for Webhelp. I appreciate any help.

This topic has been closed for replies.

5 replies

Community Expert
August 3, 2022

Thanks for posting back with your solution. 🙂 

Inspiring
August 2, 2022

I'm happy to post that I've solved the issue with the search function. When I finally got the time to dig into this again I revisited my post from 29 June 2022. I wondered if another PDF file was "offending" the search function as it did in 2016. The problem I faced was/is that now the database contains thousands of PDF files, the bulk of which have been uploaded since the search function stopped working. Thus it would be nearly impossible to try to ferret out the offending file. Then I remembered that I could exclude all PDF files from the search. I wasn't sure it that would work... but it did. I excluded all the PDF files from the search and the search function works like a charm. I also reduced my compile time from well over an hour to less than 10 minutes. 

I consulted with co-workers about the impact of excluding the PDF files from the search and we determined that since all of the documents are referenced in a topic that a detailed search of each PDF file/page was not necessary.

I may never know which PDF file brought the search function down... but given the nature of PDF files and all the different ways my vendors can save them it's probably best to exclude them regardless.

Thanks for all the help. The discussions and feedback got my brain thinking in the right vein to get this sorted out.

Community Expert
June 30, 2022

Some of the threads suggest closing robohelp, deleting the cpd and output folders, then regenerating. Have you tried that? As always, take a zip backup in case of problems.

Community Expert
June 30, 2022

Can you open the developer tools in the browser and see if there are any error messages? They probably won't be any help, but you never know.

Jeff_Coatsworth
Community Expert
Community Expert
June 29, 2022

"The search function used to work. The issue just "happened" one day." - What browser were you testing with & where is the content located? It's more likely that it's browser security "fixes" that are causing your issue.

However, your comment that a new project works indicates that maybe the issue is with your project. Is this a very old upgraded project? Have you tried testing it with different output (like HTML5)?

Inspiring
June 29, 2022

I considered the possibility of  browser security fixes as well, but when the new project worked I dismissed that idea.

This is a very old project that originated on RoboHelp 9, then upgraded to 11 and now upgraded to 17. The issue has been going on since April 2020 but we've lived with it. Now we're introducing new material that really needs the search function to operate so the issue fix has renewed life. This database is also very large over 7GB. Over 850 topics with lots of baggage .PDF files.

I have tried testing HTML5 and RoboHelp 2020, both with the same results. I do have the subscription for RH2020 but I'm hesitant to fully migrate since the problem hasn't been resolved and a test in RH2020 had the same results.

Jeff_Coatsworth
Community Expert
Community Expert
June 29, 2022

Generating HTML5 in RH2017 fails to work?