Lost RSC connection to a file after...

RSC 3.1, RH 8

We successfully branched a folder (two branches, one active, and one for archive snapshot only). A file in the active folder was apparently corrupted during the branching process, and does not appear in RSC. However, any attempt at editing the file results in this error message:

The file had additional HEAD info (shown in bold italic below) within the BODY area, interfering with the title and css info:

%26lt;?xml version=''1.0'' encoding=''utf-8'' ?%26gt;
%26lt;!DOCTYPE html PUBLIC ''-//W3C//DTD XHTML 1.0 Transitional//EN'' ''http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd''%26gt;
%26lt;html xmlns=''http://www.w3.org/1999/xhtml''%26gt;
%26lt;head%26gt;
%26lt;meta http-equiv=''Content-Type'' content=''text/html; charset=utf-8'' /%26gt;
%26lt;meta name=''generator'' content=''Adobe RoboHelp 8'' /%26gt;
%26lt;title%26gt;%26lt;/title%26gt;
%26lt;/head%26gt;

%26lt;body%26gt;
%26lt;?xml version=''1.0'' encoding=''utf-8'' ?%26gt; %26lt;!DOCTYPE html PUBLIC ''-//W3C//DTD XHTML 1.0 Transitional//EN'' ''http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd''%26gt;
%26lt;html xmlns=''http://www.w3.org/1999/xhtml''%26gt;
%26lt;head%26gt;
%26lt;meta http-equiv=''Content-Type'' content=''text/html; charset=utf-8'' /%26gt;
%26lt;meta name=''generator'' content=''Adobe RoboHelp 8'' /%26gt;
%26lt;title%26gt;Charles River IMS Online Reference%26lt;/title%26gt;
%26lt;link rel=''StyleSheet'' href=''crd_start.css'' type=''text/css'' /%26gt;
%26lt;/head%26gt;

%26lt;body%26gt;

Neither this file, nor a replacement uncorrupted version, can be edited. How can I get RSC to ''remember'' this file?

Lost RSC connection to a file after...

We found the issue that was preventing the viewing of this file: it was hidden (I don't know how, other than some network glitch during the branching process),

There's a behind-the-scenes, ''master'' that monitors all changes, and which can only be seen by viewing the ''raw root'' view.

Enabling the ''* raw root'' view will display the ''Views'' folder, which includes all the other views. The file was listed there, greyed out, and able to be unhidden.

Case solved. Phew!

Good luck,

Leon

Lost RSC connection to a file after...

This has happened to us a number of times - where the root.fpj becomes corrupted in response to someone renaming a file, and RoboHelp or RoboSource automatically ''hides'' all of the htm files in a project. We have to go into the raw root view and make them visible. Not sure why this happens.

Oh, wow! We actually did have root.fpj issues when we first started

using RSC, so this might not be a specific branching issue.

I suspect a combination network/anti-virus software issue (Kaspersky has

always been pretty aggressive, but I can't get IT to configure it to be

more forgiving).

Thx for the further info.

Good luck,

Leon

So you had root.fpj problems as well? How did you resolve them, and do you still have them?

One team in our group had them once in the beginning, but not again. My team (specifically me and another team member) have them all the time. In fact, I can't rename any file in the root without having the issue occur. I will look into the virus scan issue, but if you have any other ideas, I'd love to hear them.

The Adobe people say they have not seen this and cannot reproduce it in their environment, so they can't provide any info, but it is making us wonder whether to retain RSC, or go back to using local copies of RHelp projects.

I really hate to abandon source control, because not only is source control good practice, but it has come through for us a number of times. However, the unpredictable and destructive nature of this problem understandably has my teammates scratching their heads and wondering if it didn't cause more problems than it solved.

Thanks,

Elizabeth

''How did you resolve them, and do you still have them?'' Brute force!

Actually, a combination of backed-up copies and manual editing (multiple tries required at times) cleared things up, and those have not recurred. We've had little choice but to stick with RSC, since our outfit is extending the amount of versions and branches, so we have to follow suit. And we prefer RSC to Perforce (the developers' choice), which has never seemed to play well with RoboHelp.

Good luck,

Leon