Internal error encountered, Failed to generate Printed Documentation.

[Guest]

I created a webhelp by exporting HTML files from a wiki and using HyperText Studio and then used Adobe RoboHelp 7 to create my current version of webhelp. The wiki and HyperText Studio worked well with embedded blanks in file names and with some other characters that RoboHelp appears to consider illegal.

While working with the files I often received a warning message that a " " file was referenced by another file and would not be displayed in Project Manager. I corrected all the file names by replacing blanks with underscores and looked for specific bad characters in all of my HTML files from which I generated the webhelp. I corrected the file names within RoboHelp, which also fixed the links. I manually fixed the names of two graphics files and corrected the occurrence of their names in my topics.

Most of the weird characters (represented by %2C, for example) seemed to be present in excessively long anchors for my links. They were generated by the wiki.

The webhelp is generated.

Printed Document is not generated.

I am at my wits end and a deadline is coming real soon. Please help.

The log file I received is:

Starting to build Printed Documentation...
Printed Documentation processor 7.00.145

Building \\Cos-hq-onyx2\!cabinet1\Technical Documents\Tech Docs\U5\U5.0\Working_Oct_2008\Web_Agent_and_Supervisor_Online_Help\Web Agent and Supervisor Guide\!SSL!\Printed_Documentation\Web_Agent_and_Supervisor_Guide.doc ...

Preparing to create Printed Documentation...
Clearing output folder...
Preparing files for Print Document...
Copying files...
Updating files...
Finished preparing in 8 seconds.
Preparing environment...
Cleaning up temporary files...

Internal error encountered, Failed to generate Printed Documentation.

[Peter Grainge]

Were you an undertaker? Burying files that deep is almost award worthy.

First I have to ask if that target is local (OK) or network (not OK). Both project and output must be local.

With the project local, create a folder outside of that structure such as C:\Print and generate to that.

Stick with just creating a Word document while you have this problem, no PDF. We can come back to that.

[Guest]

Peter,

You are a real gem. Thanks.

By the way, I thought the problem was that I overlooked to check for broken links after fixing the file names and anchors. I fixed the only broken link and still had the same problem.

[Guest]

Peter,

About the depth of my folders and working in the network:

I work in the network because everything is automatically backe up and it simplifies sharing work in case I ever another colleague in this company's Doc Team.

I use the folder structure that RoboHelp provides as a default.

[Peter Grainge]

RH is not designed to work on a network so the reasons are academic. Work that way and you are going to have these problems. For backups, I simply zip up the folder at the end of the day and put it on a network. Or to be really honest, a utility does it for me.

To work with others on the same RH project, no matter where it is located, is also courting disaster unless you are doing so via source control.

You define the location when you create projects. I think the first time RH is run it may offer My Documents but it certainly does not point to any network location.

The solution to the problem is to move things. If you don't want to do that, then RH will continue to break.