Permissions required for RoboHelp Server 7

[hughbetcha]

Came accross this Adobe tech note for RoboHelp Server 6:
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb400352&sliceId=1

It states that RoboHelp Server needs access to folders on the file system and needs user accounts provided by the server system to execute processes.

Does this process need to be followed for RoboHelp 7 Server as well?

I am encountering errors when I try and publish to the server. When I go to the webpage it says the server has been successfully created, but when I publish a project I get a Connection Failed error. Not sure if this error has anything to do with permissions or if there is something else causing the error. I did use the RoboHelp Server Administrator page to add me as a user. I've ensured my Server Name was entered correctly in my project.

Thanks.

[johndaigle]

Hi. Sorry to see your post so late. You may have already found an answer.
Basically, Adobe RoboHelp Server 7 has streamlined the server software installation. All those funky permissions issues outlined on the Knowledge Base article are all done through the basic install wizard in RH Server 7. Note: That's on the SERVER side of things.

Now, with regard to the AUTHOR side. As a user, the Web Admin will need to include you in the IIS Publishing and Reports group. A "connection failed" error from the author's desktop machine trying to publish suggests to me a permissions issue that must be set up by the network/web admin. Sometimes there are firewalls that people forget to resolve that has nothing to do with RoboHelp (client or server). Once the permissions are set up correctly you should have no problem publishing to the RH Server 7.

Thanx
john

[hughbetcha]

Thanks for your reply. My IT guy decided to start over and re-install the server and run the pre- and post-scripts. That seemed to do the trick. No more Native Error when publishing. I thought those scripts were just required for RoboHelp 6, but unless he did something different, he claims the scripts fixed the problem.

[johndaigle]

Great. Glad to see that was resolved. I know permissions can be frustrating.