I'm getting the same problems as nu_sheck and Scott_I. Plus
the server is bombarded with ProtocolHost.exe errors until IIS
curls up and dies. I'm trying to upgrade to RoboHelp Server 7. I
thought I had an installation error. Maybe it is installed
correctly as I'm getting the same errors as everyone else.
I'm coming from versions 3 and 4 of RoboHelp Server. I've
installed RoboHelp Server 7 on Windows Server 2003 SP2. IIS 6.0 has
a wonderful feature in that the application pool can be configured
to restart for various reasons.
I've read here that you need to have the Windows Indexing
service running as well as the Robohelp Windows service. Both are
running under the default account, LocalSystem.
The application pool is also running under the default
account, NetworkService.
I have excluded both the C:\WINDOWS\Temp and Robohelp product
files from the scans of our anti-virus program.
In addition to the thousands of RHS*.tmp files I also get
JET*.tmp files in C:\WINDOWS\Temp. I'm guessing that these are from
the jet engine ACCESS database.
If the Microsoft Indexing service is needed by RoboHelp, why
isn't it configured? Should the Indexing service exclude
C:\WINDOWS\Temp?
We move our INETPUB folder to the D: drive. We also have a
D:\Program Files folder where RoboHelp is installed. We have two
web sites (Application Help Site and Business Help Site) using the
default application pool.
From the forum I see that the ProtocolHost.exe errors began
with version 6 and are still present in version 7. My understanding
is that the RoboHelp Windows service is a feature of versions 6 and
7.
We use RoboHelp with our local CRM application. I'd like to
know if anyone is using RoboHelp Server 7 on Windows Server 2003 in
Production.
Thanks for your help.