Skip to main content
A
Anonymous
September 23, 2011
Question

Cannot Publish to Robohelp Dev or Prod Server after monthly server reboots.

  • September 23, 2011
  • 1 reply
  • 779 views

Hello All,

I have a strange behavior occuring in Robohelp.  We are running Robohelp v8 server.  We have approx 5 contexts defined with the corresponding number of projects.

After every monthly server maintenance night server reboot to apply MS patches, the next day the Robohelp team that publishes the projects cannot publish. However the problem only occurs with one of the projects.of the projects.

This has happened now for 3 months. Nothing changes on the Robohelp client side.  The only thing that happens is the Robohelp dev and prod server get rebooted.

We are using RoboSource control 3.1.


Warning: Failed to publish to "Robo Test Server". reason: Unable to connect to the RoboHelp server on devservername:8080/KPIF_Medical_Review/server. If RoboHelp Server is not being used, generate WebHelp instead. More information on RoboHelp Server is available in the help file..

Warning: Failed to publish to "Robo Prod Server". reason: Unable to connect to the RoboHelp server on prodservername:8080/KPIF_Medical_Review/server. If RoboHelp Server is not being used, generate WebHelp instead. More information on RoboHelp Server is available in the help file..

So what I have done as a workaround on both servers is go into the servers. Stop the apache tomcat service:

rename the directory: F:\Adobe RoboHelp Server 8\KPIF to KPIF.old

restart the tomcat service.  It recreates the KPIF directory.

I then have to go into Roboserver admin and recreate the groups and users that have access to that project for admin, publishing and reports.

That gets them back up and running but It is time consuming and tedious and I am hoping that someone else has seen this problem and has an easier solution.

Please help!

Thank you

Steve

This topic is closed to new replies. Start a new post to keep the conversation going.

1 reply

johndaigle
johndaigle
Legend
September 23, 2011

Hi, Steve

This is a new one on me! I assume you do mean "contexts" and not "Areas", right.

You mention only one of the projects is affected. Is that "owned" by a particular author and does that author have the proper network permissions from their desktop to the server? I just mention this because "Unable to connect" message typically occurs because of a permissions issue somewhere. Also, it doesn't seem like it would make any difference, but can you see any differences in the way the author is using RoboSource Control with regard to the problem project? Do they have any other issues (with RH or any other app) that happen after MS updates?

Let me know and I'll forward this to an Adobe engineer and see if we can figure it out.

Thanks

John Daigle

Adobe Certified RoboHelp and Captivate Instructor

Evergreen, Colorado

www.showmethedemo.com

John DaigleAdobe Certified RoboHelp and Captivate InstructorNewport, Oregon
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices