Skip to main content
andrem2903623
Known Participant
March 5, 2020
Question

RH Server install issue on new server

  • March 5, 2020
  • 3 replies
  • 458 views

Our IT has run into an issue trying to reinstall RH Server onto a new server. We are running RoboHelp 11 and the RH Server software that came with it is not installing onto the new servers we are upgrading to. I believe the new servers we are upgrading to is the latest Windows 10. We have had issues publishing from our upgraded Windows 10 to an older version of Windows on the server. We found a workaround for that by using a Virtual Machine on our laptops.
Now that our servers are upgraded, RH Server is not installing. I checked the RH Updates (https://www.adobe.com/support/robohelp/downloads.html) to see if there is a patch for RH Server and there isn’t one available.
First question. Does anyone know a workaround or a patch to use?
Second question. If we do not want to upgrade everything to RH 2019 and RH Server 10, what alternative software can we use to replace RH Server and keep RH 11?
Any help would be greatly appreciated.
Thanks,
Andre

This topic has been closed for replies.

3 replies

Community Manager
March 5, 2020

Hi,

 

I have sent you the private message with our contact details. Requesting you please connect with us so that we can help you with the installation issue.

 

Regards,

Mayank

johndaigle
Legend
March 5, 2020

Because database synchronization is involved when using Rh Server, I don't think you'll be able to simply manually copy/paste the published output to the server. 
Regarding patches, be sure to check out this update:

https://blogs.adobe.com/techcomm/2017/09/robohelp-server-10-2017-update-1.html

Meanwhile, I will ask someone at Adobe for some assistance on this.

John Daigle

Adobe Certified RoboHelp and Captivate Instructor

1395 NE Newport Heights Dr. 
Newport, OR 97365
John DaigleAdobe Certified RoboHelp and Captivate InstructorNewport, Oregon
Jeff_Coatsworth
Community Expert
Community Expert
March 5, 2020

I suspect your workaround is to publish locally & then manually transfer the files to the RH Server location.