Skip to main content
The Atom Proj
Participating Frequently
November 21, 2024
Question

Upgraded RoboHelp from 2022.3.93 to 2022.5.28 - now has PDF Error in fetching reviews

  • November 21, 2024
  • 5 replies
  • 980 views

I upgraded from Robohelp 2022.3.93 to 2022.5.28 and it said it had to update the project. After doing so I can no longer generate PDFs from my project. 
I get the following dialog box: ** I replaced the acutal document name with [DocumentName] **

Failed to generate [DocumentName] PDF. Check log for more details.

 

The ehtml file shows it make the last page of the content as a .htm and then says:


Error: :80:7: Unknown word

Error: Failed to generate [DocumentName] PDF. Check log for more details.

 

Then looking in the logs_nnnnnnn.log files it shows the following error: 

Error in fetching reviews {"error":{"statusCode":404,"message":"{\"reason\":\"not_found\",\"message\":\"The requested resource could not be found\"}"}}


Nothing else in the logs_ files looks out of the ordinary.

I can also open up the old instance of this project in 2022.3.93 and it creates the PDF files as expected.

Additionally I can open up the Adobe Sample project in 2022.5.28 and create the PDF as expected.

 

I have selected various different directorys to output to, I have moved the entire project around on my system, and I have reviewed the output to show that every bit of the content gets created. It just doens't convert the resulting .htm files to a singular PDF.

    5 replies

    Peter Grainge
    Community Expert
    Community Expert
    February 3, 2025

    Is the tag in the TOC? That would allow it to generate but not show in the TOC. Generate again and search for it. That would further confirm the theory.

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

      

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Inspiring
    February 3, 2025

    Well, yes - we have tags in the ToC, and in the topics themselves, both on topic level and on content level. But that isn't different between this awful topic and all the others. And I already checked each and every code line in it, even compared the last working output to the one that passed today (when I skipped the condition expression).

    And I also set up a new condition expression and checked all sets we had for years on code level (XML) in comparison. There was an error in it! The group of tags had the attribute "Exclude" in it what doesn't make sense at all. On top of that, the first <tag> entry had the wrong attribute: I set that up as "Exclude" which was shown in the UI correctly, but in the XML code it was registered as "Include".

    There's definitely something wrong in that procedure, but correcting it manually didn't lead to a successful output. I'll better check the XML files of the condition expressions as they were in Mai 2024, just before updating to RH 2022 Upd 4. Back then, everything was fine with that topic, and I know that for sure because we're archiving every published output. That's how I found out about the missing topic: It is missing since June 2024, right from the first output we generated after updating RoboHelp.

    Inspiring
    February 3, 2025

    And sometimes there are other differences regarding Condition Tags between what appears in the UI and what I set up:
    For another topic (not the awful one that goes misssing all the time), in the Content Properties panel a different (wrong) tag shows than in the Properties modal. There seem to be some glitches in the software. I think I need to report a bug and provide some code and screenshots for that.

    Peter Grainge
    Community Expert
    Community Expert
    February 3, 2025

    I heard you say tags can be ruled out but nonetheless try generating without any applied.

     

    Also create a new TOC using autocreate for speed. The topics will be in the wrong place but the test is whether or not it generates the missing topic.

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

     

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Inspiring
    February 3, 2025

    OMG! Yes, you're on the right track there, Peter:
    If I leave out the condition expression during output generation then that #+'*$&%/&§"! topic is processed perfectly!
    I already reset the condition tags in that topic but now I can play around to find what's wrong there so I can put on the condition expression again. We need it because all the topics are tagged in some way or the other, and for years that worked fine.

    Inspiring
    January 29, 2025

    Hi @The Atom Proj, could you solve the mystery already? We're having a mysterious trouble with an output from a large RH 2022 project, too: After updating the project to RH 2022 Update 4 (and later to Update 5), a single topic is too shy to come out, even though it has been unaltered for years. It's in the log with the "Updating..." state but never gets to the "Finished updating..." state (like all the hundreds of siblings do). Therefore it's not put into the output folder anymore. I checked that thoroughly: this topic is the only one that falls off the wagon during the generation process - not a very complicated or long one, just a some text and a table in it.
    Thanks to your earlier posting here, I found that \RHTMP log file folder (that place can't be found via the software documentation) and was hoping to get some more information on the background processes. But unluckily it doesn't say anything about the cause here. 

    Jeff_Coatsworth
    Community Expert
    Community Expert
    January 29, 2025

    @gbr_555 - is the sample working for you? If so, it's definitely some issue in your project. At that point, I would be going through the divide & conquer route with a copy of the project until you isolate the topic. Then you can start tearing it apart to find the offending code.

    Peter Grainge
    Community Expert
    Community Expert
    January 29, 2025

    See Divide and Conquer in Item 1 in Generating Outputs.

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

     

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Peter Grainge
    Community Expert
    Community Expert
    November 22, 2024

    Can you share the project? If you can, then 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.

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

      

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    The Atom Proj
    Participating Frequently
    November 22, 2024

    No, I'm sorry I can not. While the resulting files the RH project creates are all public facing help documents for a commerical software product, the RH project itself is considered propritary source code and can not be shared. 

    It's got to be some setting in this project that the latest version of RH doesn't like that is causing the issue. I just can't find any PDF related errors in any logs that point to an issue. Maybe I'll run debugview and see if any consol messages are created...

    Peter Grainge
    Community Expert
    Community Expert
    November 22, 2024

    Egh? What is in the source that is proprietary other than what will be in the output. Hey ho, up to you.

     

    What I would do first is create two copies of the TOC and delete different halves, then generate both and see if one works and one doesn't. Repeat with the one that doesn't work until you track down the problem. 

     

    I would also try a new preset and new templates, more than one.

     

    Is your project on a local drive and are you generating to the same drive? All without source control?

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

      

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Peter Grainge
    Community Expert
    Community Expert
    November 22, 2024

    I haven't seen any other report of this and the fact you can generate the PDF from a sample points to the issue being in your project. The only PDF change in Update 5 was related to a different PDF issue. There were also some PDF changes in Update 4 but again they don't look relevant. See https://helpx.adobe.com/robohelp/kb/fixed-issues.html

     

    I note that the content of this post seems to relate to PDF generation generally but the title includes "reviews". Are you talking about a straightforward PDF or the PDF created for the Reviewing feature?

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

     

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    The Atom Proj
    Participating Frequently
    November 22, 2024

    It's related to PDF generation. The "reviews" error is the only obvious error across multiple logs I could find so it may be unrelated.
    I reverted back to 2022.3.93 and opened up the project (after it was updated); It warned me, but it opened fine and it was able to create the PDF just fine.  I'm going to roll back to my last save before the upgrade and stick with 2022.3.93 until I have the time to address the PDF issue. 


    There is no doubt it's related to my specific project, but what the issue is and why it works for one version and not another is the mystery. I made a test pdf export from this same project and it still wont work. One page pdf or 50 doesn't matter so it's something inherent in this project that needs to be fixed. 
    This project is made up of thousands of pages created under various robohelp versions for over a decade now so it's no wonder it continues to be a problem every time there is a new release of RoboHelp. 

    I'll look through the release notes again for all PDF related changes for the past few releases and hopefully isolate the issue to something that I can resolve. I also emailed adobe directly about it so hopefully they will have some insight to resolving it.