Skip to main content
R
RH 11 GS
Participant
September 23, 2021
Answered

Printed Documentation Failure

  • September 23, 2021
  • 2 replies
  • 301 views

I have a project that was created in RoboHelp 15 and was recently converted to RoboHelp 2020.  I had no problems generating printed documentation of the project in RoboHelp 15, but I am unable to generate the printed documentation in RoboHelp 2020.  Note, I have a different project that was also converted to RoboHelp 2020 and have no problems generating printed documentation of that project.

 

I googled this error and found threads that talked about the directory name being to long, so I shortened it -- did not fix the problem.  I also saw a thread that talked about the mso-bookmark property in the .css being an issue, but that property does not exist in my .css.  I chatted with an Adobe support person who recommended that I change my password and re-login and also to reinstall the Robohelp software.  Neither of those solutions were of help.  I am including the contents of the log file below.  I am also attaching my .css file file to assist in troubleshooting.  I tried to post the .preset file, but it won't let me attach that file.  Any thoughts from anyone (since the error message is less than helpful)?

This topic has been closed for replies.
Correct answer RH 11 GS
Thank you to all the responses that I received for this issue. The issue
turned out to be the version of Java that I had installed. Once I
installed Java 17, the printed documentation generated as expected.

2 replies

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
September 27, 2021

I have deleted the log text from the body of your post and attached it as a text file to save a crazy amount of scrolling. 🙂

 

As the text includes Java Found, I assume you are try to generate a PDF document rather than Word.

 

I don't understand why you were told to change your password and reinstall. If both outputs were failing, reinstalling might have been worth a try but not when one project is working.

 

As well as what Amber has suggested, you could try changing the CSS. To make it easier to test, create a copy of your project to work on. Go to the topic list and select all topics. Right click and select Properties and delete the CSS attached. Then attach the default CSS. Your output will look rubbish but all we want to learn is does the PDF then generate.

 

Post back when you have tried both suggestions.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
R
RH 11 GSAuthorCorrect answer
Participant
September 27, 2021
Thank you to all the responses that I received for this issue. The issue
turned out to be the version of Java that I had installed. Once I
installed Java 17, the printed documentation generated as expected.
A
Community Expert
AmebrCommunity Expert
Community Expert
September 27, 2021

Given you have another upgraded project that generates correctly, it seems project specific.

 

I know CSS oddness from upgraded Classic stylesheets can prevent the word output generating. But the css you posted seems fine. If there are any other css files in your project, make sure they aren't assigned to any topics, master pages you're using or in the output preset itself. This should ensure the css files aren't causing the issue.

 

I remember other people have reported issues with inline styles on their tables, and on image maps. If you're using either of those, perhaps check the code for anything strange. You could also use condition codes to exclude them, to see if that made a differnce,

 

You can also try the divide and conquer method to isolate a specific topic that might cause the issue. Duplicate your existing table of contents twice. Delete half of the entries from the first copy, and delete the other half from the second copy. Try generating each in your output preset. If one generates and the other doesn't, repeat the process for the toc that doesn't work, until you can isolate a specific topic.

 

 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices