9
Replies
9
9
Replies
Advisor
,
Hi, Chris!
I just set up RH Server 7 on my little web server last night. I was pleasantly surprised how smooth it went. Basically, I uninstalled the old RH Server 6, rebooted and installed RH Server 7. I didn't touch permissions (that's a first!). I'm using Windows 2000 Server and the built-in Access database.
Now for your issues. Since you are already familiar with this, some of my speculation may be obvious to you, but I'll see if we can figure this out.
I assume you set up a WebHelp Pro Layout and used the Publishing wizard to set up a site with a username and password that is associated with the RoboPublish Group that is automatically created by the server install wizard? That's definitely critical. This is because even though the install program sets up the groups and server permissions automatically, it can't know which user is assigned to a particular group. That has to be done by the server admin.
You would also want to make sure your PC connection is making it through any firewalls and domains along the way to the server (sounds obvious, but I've seen this happen)
On the HHCTRL issue. When you say "Event Viewer" are you referring to the Windows 2003 R2 Server's official Event Viewer, or were you just using that term to describe the Troubleshooting list of Robohelp Server errors?
Regardless, it is strange that it would appear. The HHCTRL refers to Microsoft's HTML Help Active X Control and is what enables the compiled help .CHMs. I can't see where that would impact a WebHelp Pro server event, but I'll ask around. As you may know, many of the warnings and alerts are often "benign" so it's hard to say whether this impacts anything or not. It could be that Windows Server 2003 throws more "security" warnings?
Anyway, verify that your username is assigned to the RoboPublish Group and let me know.
Thanx,
john
I just set up RH Server 7 on my little web server last night. I was pleasantly surprised how smooth it went. Basically, I uninstalled the old RH Server 6, rebooted and installed RH Server 7. I didn't touch permissions (that's a first!). I'm using Windows 2000 Server and the built-in Access database.
Now for your issues. Since you are already familiar with this, some of my speculation may be obvious to you, but I'll see if we can figure this out.
I assume you set up a WebHelp Pro Layout and used the Publishing wizard to set up a site with a username and password that is associated with the RoboPublish Group that is automatically created by the server install wizard? That's definitely critical. This is because even though the install program sets up the groups and server permissions automatically, it can't know which user is assigned to a particular group. That has to be done by the server admin.
You would also want to make sure your PC connection is making it through any firewalls and domains along the way to the server (sounds obvious, but I've seen this happen)
On the HHCTRL issue. When you say "Event Viewer" are you referring to the Windows 2003 R2 Server's official Event Viewer, or were you just using that term to describe the Troubleshooting list of Robohelp Server errors?
Regardless, it is strange that it would appear. The HHCTRL refers to Microsoft's HTML Help Active X Control and is what enables the compiled help .CHMs. I can't see where that would impact a WebHelp Pro server event, but I'll ask around. As you may know, many of the warnings and alerts are often "benign" so it's hard to say whether this impacts anything or not. It could be that Windows Server 2003 throws more "security" warnings?
Anyway, verify that your username is assigned to the RoboPublish Group and let me know.
Thanx,
john
Advisor
,
Hey, Lord Kemsley!
The error 500 is not a specific RoboHelp Server message. It is a generic "catch-all" error thrown by the IIS web server that simply means it cannot deliver a request. Unfortunately the error doesn't give many clues.
That said, your message is a classic example of permissions not being set right somewhere along the line. In addition to users and groups permissions make sure your PC can "talk" to the server via whatever hoops it needs to go through (firewalls, etc.) Sometimes it seems like all the "i"s are dotted, but there's a "t" not crossed somewhere.
To test communication, you might also put a plain HTML page on the site. Manually make a dummy page (default.htm not default.asp) and manually place that in the root of the website. (In other words, don't "publish" it from RH) Then type that page in your web browser to see if the website comes up. (Something like http://123.45.66.77/default.htm ) If you can access that from your web browser on your machine that will at least tell you the website is "live" and accessible to your PC.
Sorry I can't be of more help. Let me know if you get anymore clues.
Hope this doesn't sound like "selling" but your IT folks should also know that RH Server 7 is way easier to install permission-wise than RH 6. So you might look into upgrading. (the RH client authoring apps would have to be upgraded as well). Fortunately it's not expensive ($79 for the authoring app upgrade and $160 for the Server)
Thanx,
John
The error 500 is not a specific RoboHelp Server message. It is a generic "catch-all" error thrown by the IIS web server that simply means it cannot deliver a request. Unfortunately the error doesn't give many clues.
That said, your message is a classic example of permissions not being set right somewhere along the line. In addition to users and groups permissions make sure your PC can "talk" to the server via whatever hoops it needs to go through (firewalls, etc.) Sometimes it seems like all the "i"s are dotted, but there's a "t" not crossed somewhere.
To test communication, you might also put a plain HTML page on the site. Manually make a dummy page (default.htm not default.asp) and manually place that in the root of the website. (In other words, don't "publish" it from RH) Then type that page in your web browser to see if the website comes up. (Something like http://123.45.66.77/default.htm ) If you can access that from your web browser on your machine that will at least tell you the website is "live" and accessible to your PC.
Sorry I can't be of more help. Let me know if you get anymore clues.
Hope this doesn't sound like "selling" but your IT folks should also know that RH Server 7 is way easier to install permission-wise than RH 6. So you might look into upgrading. (the RH client authoring apps would have to be upgraded as well). Fortunately it's not expensive ($79 for the authoring app upgrade and $160 for the Server)
Thanx,
John
Resources
RoboHelp Documentation
Download Adobe RoboHelp
AdChoices