Skip to main content
P
pjv
Inspiring
December 8, 2009
Question

RH7 WebHelp Pro Index not working when viewed from RH Server 8

  • December 8, 2009
  • 1 reply
  • 1110 views

I've got a RH7 project that was published to RH Server 8 using the default Access database. When I view the project from the server, the Index, which is 444kb, dies. The 1st 20-30 keywords and subkeywords display in the index panel. When I try to search on a keyword, nothing happens. If I use the scroll bar to move down, a message "Loading Index..." displays but nothing happens -- waited over an hour but nothing moved. When I open the same project on my local drive, the Index works just fine.

I spoke to Adobe support and they said to try a sample project. Well, I did and an index of about 104-140kb worked fine on the server. However, as it got up to 140kb, I started to see the Loading Index... message but it flashed by quickly and I was still able to search by keyword.  Then I built the index up to 190kb and the same problem that occured in my larger project happened.

Is there a maximum Index size that is allowed when your project is published to the Access database?  There's no RH Server 8 documentation regarding maximum sizes for the Access database so I'm really annoyed. 

This topic has been closed for replies.

1 reply

P
pjvAuthor
Inspiring
December 8, 2009

Sub-comment to my original posting. We're also having the problem with Apache Tomcat stopping and starting.  I've forwarded the 2 discussions regarding how to adjust the size to my tech support person. So this might be an issue with the Apache Tomcat and the fact that we're using the default Access database.  I'm attaching the Tomcat log from 12/08/09 if that helps.

tuls_garg
tuls_garg
Inspiring
December 9, 2009

Hi Paula,

Did you try increasing java heap space and perm space?

Tulika.

RoboColum_n_
RoboColum_n_
Legend
December 9, 2009

Although this is not documented it is widely accepted that running on an MS Access database is not great for a production environment. We too have suffered the "loading" index although it does seem to be intermittent. We will probably go over to using SQL Server instead before go live.

  • Read the RoboColum(n) for a tips, tricks and musings on the Technical Communication Suite products.
  • Follow the RoboColum(n) on Twitter
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices