Copy link to clipboard
Copied
Environment
Windows 7 Enterprise, Service Pack 1, 64-bit operating system
Office Professional Plus 2010 Versions 14.0.7106.5001 (64-bit)
RoboHelp 10: 10.0.0.287
Visual Studio 2010 Professional. I open RoboHelp from within Source Control (have been doing it for two years).
Problem
Sometime after moving to RoboHelp 10, and even after successfully generating Printed Documentation output, I encountered a major problem generating Printed Documentation from RoboHelp: “Internal error encountered. Failed to generated Printed Documentation”. The error occurred when I tried to generate Printed Doc using my default TOC, which looks something like this:
Topic A
Topic B
Book 1
Book 2
Book 3
Topic C
Topic D
Based on an old Peter Grainge reply to someone about a similar problem, I removed all but the first topic from the Chapter Layout pane and generated the Help. Everything was fine until I got to the topics after Book 3. At that point everything started to fail again. When I removed Topics C, D, etc. from the Chapter Layout pane, the output was built successfully.
I tried moving Topics C, D, etc. to the top of the Chapter Layout pane, and got the same error. I tried creating a new folder and put Topics C, D, etc. into that folder. Failure after failure.
As an experiment, I removed all the Topics C, D, etc from the Chapter Layout pane, but then added them to the Print Document Section Layout pane (not where I want them). The Printed Documentation built successfully.
During attempts to build with Topics C, D, etc. in the Chapter Layout pane, I kept getting a Word error: Word is trying to recover your information. After that there was always a failure.
Selecting PDF as the output did not work when the Topic C, D, etc. files were at the bottom of the Chapter Layout pane.
I create a new TOC and a new Printed Documentation SSL. Failed to generate.
As a matter of reference, I've been generating Printed Documentation from the same TOC for more than a year and so cannot figure out what has changed in RoboHelp or Word to cause this grief .
Has anyone experienced anything like this?
Carol
Copy link to clipboard
Copied
Does it work with one of the sample projects?
Copy link to clipboard
Copied
Thanks for your reply, Jeff.
Yes, I created an "online manual", copied several single topics to the bottom of the Chapter Layout pane, and generated PDF and Word successfully.
However, I'm not sure that the test is valid: While I created this sample project locally, I work in my project in Source Control. In addition, the sample project contains significantly fewer files than are in my project.
Two of the quirks in my project are:
For a while I thought that it was because the "Critical error of Source Control Provider. Please restart IDE." message was hiding behind the application and I couldn't get to it fast enough to click OK. When you don't realize the message is hiding out on you, RoboHelp just sits there, waiting, and you end up thinking that it's crashed.
Since I'm also getting the "Microsoft Word is trying to recover your information" message (which I did not get with the sample project), I thought it might be a Word problem, perhaps related to the documentation template that is our default. But that makes no sense considering that I can build the Printed Documentation based on the two quirks above.
Carol
Carol
Copy link to clipboard
Copied
So I'd be tempted to think that not everything you need is checked out of source control when it comes time to create printed documentation. Sorry I can't help you further - I don't use any SC & I never create PDFs out of RH (FM is sooo much better at doing that!)
Copy link to clipboard
Copied
Not so much of the "old Peter Grainge".
What happens if you generate without topics C and D? I'm wondering if what has changed is the content in those toipcs.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
Haha, young Mr. Grainge! Sorry about the misplaced modifier.
Yes, I built the Printed Documentation without including those topics in the Chapter Layout pane. I also built the Printed Documentation with those topics by selecting them in the Section Layout pane. And at one point the other evening I built the whole thing with those pesky files at the top of the pane.
This morning I checked out all the files and attempted to generate "Printed_Documentation_for_Tech_Review" with the entire TOC structure. The pesky files are from "Abbreviatioons" on. Internal error, failed to generated Printed Documentation.
I removed the files from "Abbreviations" on, from the Chapter Layout pane. Printed Documentation was built successfully.
I added "Abbreviations" to the Chapter Layout pane as the last topic in the "Administration Console" book. Failed to generate.
I moved "Abbreviations" to the top of the Chapter Layout pane. Failed to generate.
I moved "Abbreviations" to the Section Layout pane. Built successfully, which leads me to believe that there is nothing wrong with the file.
The build failure is always proceeded by the following Word error message. I'm hard pressed to believe that this is a Word problem since the build works for all the other topics and for "Abbreviations" when it's part of the section layout.
FYI, "Abbreviations" is a very simple topic.
The Word output is 307 pages.
I just copied "Defining Complex Filters" to the "Working with Projects" book in the Chapter Layout pane and it built successfully! I had left "Abbreviations" in the Section Layout pane for this generation.
I've now removed "Abbreviations" and regenerated with "Defining Complex Filters" still in place and it has built successfully.
I added "Abbreviations" to the "Working with Projects" book in the Chapter layout and RoboHelp is now spinning its wheels "updating images". I am going to have to Ctrl+Alt+Del the application and will probably have to restart my computer .... RH will think that the output is still being used unless I restart the computer .
When I'm up again, I'll try adding other topics (not "Abbreviations") to the "Working with Projects" book and see what happens.
Carol
Copy link to clipboard
Copied
You left this thread at a point where you were going to try again later. Does your silence indicate progress?
If not, can you take a copy out of source control and send it to me. See the Contact page on my site and send the project as instructed there. Do make sure you include a link to this thread and please do not email the project direct.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
Dear Peter,
Thanks for following up. Last Friday I finished extensive testing on my own and working with RoboHelp Support. Here's what I sent to Support this morning.
If after reading this screed, you think it worthwhile for me to get a copy from Source Control for you to look at, I will do so. Thanks for offering to look at it.
Printed Documentation failed multiple times with the default Table of Contents, which contains all the topics in the project. TOC specs are as follows:
Generation to Printed Documentation does NOT fail for other, module-specific TOCs, nor to WebHelp Pro SSLs for the same sets of topics. In addition, and perhaps more important, generation to Printed Documentation does NOT fail with “Generate Individual Documents” selected, or when there are approximately fewer than 259 files in the TOC.
(I know that we should generally post non-RH issues to other forums, but in this case I wanted to include all potentially related issues in this posting.)
Carol
Copy link to clipboard
Copied
Try the version of the project I have uploaded back to you. Email yesterday refers.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
I opened the project in RoboHelp -- without going through Source Control -- and changed the file name to "01_PeterCarol".docx". Results: "Internal error encountered. Failed to generated Printed Documentation." The error is preceded by this error: "Microsoft Word is trying to recover your information."
What version of Word did you use to generate the output successfully? As noted earlier in this thread: "Microsoft Office Professional Plus 2010 Version 14.0.7106.5003 64-bit--Note: We repaired my current version of Word, in case that was the problem, but did not reinstall Office--we do not think that the Word version is the problem because we generated successfully with other TOCs and when generating individual documents."
Carol
Copy link to clipboard
Copied
Update: Problem resolved by installing 32-bit Microsoft Office.
Based on recommendations from Adobe Technical Support and Peter Grainge, my IT guy uninstalled 64-bit Microsoft Office and installed 32-bit Microsoft Office. I created a new Printed Documentation SSL using the default Touchstone Table of Contents (which had failed repeatedly) and successfully generated a single document.
From Peter's site::
“Windows 7 64-bit OS supports both 32-bit and 64-bit applications. Legacy 32-bit applications run in 32-bit mode, called Wow mode. Due to Windows architecture restrictions, any 32-bit application cannot interact with a-64 bit application. Currently RoboHelp 9 runs at 32-bit in Wow mode on 64-bit Windows OS. When RoboHelp (32-bit) tries to interact with Office 2010 (64-bit) it fails and RoboHelp thinks that Office is not installed.”
Here are some useful links for anyone dealing with 32-bit and 64-bit compatibility:
http://www.grainge.org/pages/authoring/rh9/using_rh9.htm
http://www.pcworld.com/article/197415/Office_2010.html (Beware of Office 2010’s 64-bit Shortcoming, written in May 2010, so some of the information may be a bit out of date)
http://blogs.technet.com/b/office2010/archive/2010/02/23/understanding-64-bit-office.aspx
http://technet.microsoft.com/en-us/library/ee681792.aspx (Office 2013 64-bit, updated July 2013, recommends 32-bit Office for most users)
Copy link to clipboard
Copied
Hi, Jeff.
Thanks. I did try checking everything out of source control. That didn't solve the problem (and I've never had to do this in the two years I've been generating Word versions from my Help project).
I typically create a Word document from the Help because tech reviewers like to be able to read the whole thing in one document and make their changes in the Word document.
I tried generating a PDF just to see whether Printed Doc would work for PDF -- might have helped to isolate this as a Word problem.
Carol