Skip to main content
J
jdcyclone1
Inspiring
March 17, 2008
Question

RoboHelp Server Service Crashing

  • March 17, 2008
  • 2 replies
  • 681 views
At random times, sometimes hours, sometimes days apart, the RoboHelp Server Service stops and our server is therefore down. We are running on Windows 2003 Server. I am using internally created databases instead of SQL. What could be the cause of this??
This topic has been closed for replies.

2 replies

J
jdcyclone1Author
Inspiring
March 28, 2008
We've found a quick fix which seems to have worked. If you go into the Windows Services and go to the properties for the RoboHelp Server Service you can set up recovery options. You can tell it to restart the service if it goes down, and it gives you the option to do this for a 2nd crash, and subsequent crashes. Since we've set this option it has seemed to be perfect. This probably isn't an ideal fix, but I guess if it makes it so the help is available for users, then it's what has to be done.
C
Cro1410
Inspiring
April 2, 2008
I've seen this type of pb reported time and time again with internally created dBs, SQL, ... . The only commonality between the different posts is that everybody encountering this pb are using hosting on a Windows 2003 server. Maybe somehting there... Never tested on a different environment
We have done intensive testing of RH server 6 and 7 on Windows 2003 and reverted to X4 because of systematic crashing. Our net admin made some pretty interesting findings on this (see history postings on this forum from Peter Buelens). Generally conclusion was that it was badly programmed :-).
For the quick fix, this could work for some but if the service crashes 20 times a day (like it did with us) the amount of up time will be very limited !
The best solution we found so far is to stick to X4 version that seems to be a lot more stable. Only draw back, we can't upgrade to RH Office version 7.
Any comments on this are more than welcome.
- Chris.
A
Anonymous
March 28, 2008
We have had the same experience Server6. Our cases has been escallated to a SR ROBO TECH who told us to got to 7.0. The problems have only got worse so we reverted to RoboEngine 4.0.

We have found using RoboEngine 4.0 that if you recreate the webserver, it solves the problem for a while until it corrupts again. We havn't been able to determine the root cause of the corruption.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices