A

Anonymous

Question

Installing RH on a Network Drive

Forum|Forum|18 years ago
February 13, 2008
7 replies
1825 views

Hi,
I know this topic has been revisited a number of times over the years. My apologies for the sequel. I am trying to explain to our network admin folks why we should not install RH 7 copies on each author's private 'H' drive. In this case, H is a network drive accessible to the author. The environment here is pretty locked down and almost all other apps are available over a network drive, rather than local. For example, MS office is run via H.
I have researched a bit, and found that RH has an underpinning of an Access db. Further, I have found that Access dbs don't do so well over networks.
Is this still true for RH 7?
Can anyone offer some tech-speak that would ward off the hounds? They are unwilling to accept the plain language, "I know it won't work."
It would seal the deal if an Adobe person could offer the "company line" on the practice.
Thanks.

This topic has been closed for replies.

H

HKabaker

Inspiring

hugh,

I don't know about RH Server, but 100 % usage is one of the symptoms you can expect when editing projects across a network.

Since you're having problems, and you have to start somewhere, you should listen to Colum.

Harvey

MergeThis

Inspiring

RH license on local machine
[Copy of?] RH project on local machine
Copies of other merged project folders on local machine (for creating relative hyperlinks)
Generate output to location on local machine (usually best not to !SSL! default)
Publish [changed only] output to location on server(s)

Good luck,
Leon

H

hughbetcha

Known Participant

quote:

Generate output to location on local machine (usually best not to !SSL! default)

MergeThis, I did this and was successful in publishing to server (previously always got 'Publishing Cancelled...Native Error' message). First I tried publishing to a folder other than !SSL!, and publishing worked. I also tried with another existing project to first delete the contents of !SSL! and then republish to it, and this also worked.

Is there any need going forward to either publish to a new output folder or delete the contents of !SSL! before publishing? I would think selecting the 'Re-publish All' checkbox would accomplish this. (Guess I don't understand why need to publish to folder other than the default !SSL!).

When I tried publishing an update to the same folder, the progress bar goes to the end and then just hangs there forever and I have to stop the process, as even cancelling doesn't stop it.

Thanks!

RoboColum_n_

Legend

Working on your source files whilst they are on a network drive may not have caused any problems SO FAR. Think of it as a game of Russian Roulette. Sooner of later, your luck will run out. Regardless of whether it solves THIS problem it sure as hell prevents others.

H

hughbetcha

Known Participant

I haven't been experiencing RH freezing up locally when working on projects which are housed on the network drive - although it does take a lot longer to open up projects and publish, as compared to our previous RoboInfo 5.

As we had been getting error messages when trying to publish, we are doing a workaround where we are 'manually' publishing by generating output then someone else copies to the server. Perhaps I should try publishing a project that is on my local machine directly to the server to see if that makes a difference.

Yes, projects are on same server as help site. It's a VM dedicated to Robo. Our problems seem to be that the server experiences near 100% cpu usage and will crash. This problem has been posted before and there seems to be issues with RH 7 Server being installed on Windows Server 2003 from some of the posts I've read.

I don't think publishing our projects from local drive will solve our problems, but may be worth a shot.

H

HKabaker

Inspiring

Hard to say, without knowing what's making the help site crash.

Usually, the problem is while using RH locally to build a project not on the local drive. RH locks up, project files get messed up.

Are your projects on the same server as the help site? Can you say whether the server crashes coincide with someone editing a project?

Harvey

H

HKabaker

Inspiring

Yes, there is an issue with having your project files on the LAN, unless you bring the entire project down to your PC while you're working on it.

What is the "RH Site" that crashes? Do you mean the place where the projects live, or the location of the output files?

Harvey

H

hughbetcha

Known Participant

quote:

What is the "RH Site" that crashes? Do you mean the place where the projects live, or the location of the output files?

Just mean our online help site crashing, so where output files live I guess.

We have about 40 merged projects. Do you recommend then, I copy all the project folders from our LAN onto my PC and then generate and publish each of them again to the server?

H

HKabaker

Inspiring

Hi, ConTextCB,

As you point out:

"Further, I have found that Access dbs don't do so well over networks."

To elaborate:

When the project files are on a network and we are working in the RH application, occasionally and unpredictably the user's PC will freeze, or RH will crash, requiring a forced reboot before you can launch RH again. Often, the project's housekeeping system gets broken. Common symptoms include topic files "disappearing," SSL output setups malfunctioning, and Printed Output failing to generate.

Other applications that manage a Microsoft Access database across a network also have sporadic lockups.

Many of our colleagues who asked this question reported back that these problems went away after they brought the project over to a PC's hard drive.

I think tech folks whose first language is tech-speak can understand this.

That said, you can safely use a code management system to check out an entire project, bringing it to the PC for working in RH, and checking everything back in on the network. This is well documented.

We haven't heard much about installing the RH application on a network and launching it on a PC. If your IT folks go that route, please post here about your experience.

Harvey

A

Anonymous

Hi Harvey,
Thanks for the info. Between the information from you and Rick, I should be able to pull together a justification for local projects.
Agan, thanks for yoor time.

MergeThis

Inspiring

Actually, there are some files that might be trouble if included in source control (some machine-specific, some not): HHP, CPD, PSS, LDB

Good luck,
Leon

Captiv8r

Legend

Hi ConTextCB

It's not the RoboHelp application files you are concerned with being on the network. Instead, it's the project files you create using RoboHelp that shouldn't be on the LAN. As long as you work with your projects while they are on your local PC, you should be fine in this configuration.

Now if your IT folks are wanting to install a single license of RoboHelp on the network and have multiple users accessing and using a single license, that is both against the licensing rules as I understand them as well as probably being a recipe for disaster.

Hopefully others will offer other insights.

Cheers... Rick

A

Anonymous

Thanks Rick. We are in full compliance with RH licenses. No worries there.
The IT dept hope is to install each licensed RH 7 copy on the LAN and to store the project files there as well. We will be using a source control system (not RoboSource or VSS!) to check in and out among multiple authors.
1) Is it the project files that make use of the Access underpinning? Or, the app itself.
2) Is it fair to say network traffic can corrupt the files by diminishing response time, increasing wait time, and causing repeat requests for data? (I must cite your article and a previous post, circa 2005 for this information.)
3) Are there project files that are user/machine-specific?
4) Ultimately, is there tech-speak that can address the "why not store the project on the LAN" question?
I am very grateful for any information you or anyone can provide.
Thanks.

Captiv8r

Legend

Hello again

We are in full compliance with RH licenses. No worries there.

Cool, just thought I'd point out the obvious with that.

The IT dept hope is to install each licensed RH 7 copy on the LAN and to store the project files there as well. We will be using a source control system (not RoboSource or VSS!) to check in and out among multiple authors.

Again, the actual application files are probably fine. Project files, no.

1) Is it the project files that make use of the Access underpinning? Or, the app itself.

Only the project files.

2) Is it fair to say network traffic can corrupt the files by diminishing response time, increasing wait time, and causing repeat requests for data? (I must cite your article and a previous post, circa 2005 for this information.)

I believe that is exactly the issue! You may wish to review fellow Adobe Community Expert John Daigle's Developer Center article. Click here to read John's article.

3) Are there project files that are user/machine-specific?

None to my knowledge.

4) Ultimately, is there tech-speak that can address the "why not store the project on the LAN" question?

Hmmm, I guess the very real risk of project corruption woes isn't techy enough to suit your IT group?

Cheers... Rick

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded