Skip to main content
J
Jess Blake
Participant
January 17, 2024
Answered

ENOENT: no such file or directory, lstat Word Output Error

  • January 17, 2024
  • 3 replies
  • 1141 views

Hi there, 

 

I keep running into the "ENOENT: no such file or directory, lstat 'C:\Users\XXXX\AppData\Local\Temp\RHTMP\[folder name]\[doc name]' error when trying to generate a word output in RoboHelp 2022. 

The output preset is a duplicate of another working Word preset. They both use the same style guide, template, and output folder. I've tried selecting the TOC that's causing the error in the working output preset and I get the same error. I think the issue must be TOC/topic-related. I've tried deleting the topics individually to find the problem one, but I've had inconsistent results (sometimes it'll generate with a topic added and sometimes it won't). 

There are no other warnings/errors in the log file, except for the ENOENT after the "Converting mergedHTML.htm" step. 

Does anyone know how to identify the problem?

    This topic has been closed for replies.
    Correct answer Jess Blake

    Thanks, but I ended up finding the solution. In a couple of my topics's source code, some lines had both inline style and a css class. When I removed the inline style, it generated without error. 

    3 replies

    A
    Community Expert
    AmebrCommunity Expert
    Community Expert
    January 18, 2024

    Here are a couple of other forum posts about the ENOENT error.

     

    https://community.adobe.com/t5/robohelp-discussions/failing-to-generate-word-output-rh-2022/td-p/13976125/page/2 - suggests a problem with ampersands in the Title field (although I could't quickly see the point number, so maybe there has been a patch since this post that contains a fix)

     

    Which reminds me, make sure you are on the latest patch of RH2022 - should be patch 3 as of today.

     

    https://community.adobe.com/t5/robohelp-discussions/can-t-generate-a-word-doc/m-p/14122784 - this one suggests checking for leftover ms code in the css file, although i would expect other errors in your log file if this was the case. But worth double-checking.

     

      A
      Community Expert
      AmebrCommunity Expert
      Community Expert
      January 18, 2024

      You could try clearing the output folder, and the folder mentioned in the error (the error one I think is supposed to be automatically deleted at the end of the generation process, but I could be wrong about that). Do it for both outputs to make sure everything's clear.

       

      Also, you could try restarting the computer to make sure all applications and services are reset, then try generating the problem output. It's possible that a Word service is still running, and RH gets upset because it can't have two going at the same time. (also, I've had problems with outlook incorrectly holding on to a file reference and causing things to fail in older versions, for example.)

       

      If those don't fix the issue, the divide and conquer approach seems like the way to go. First, make sure "Include all referenced topics" is deselected in the problem output and try to generate. This rules out problems in some topic that is not included in your TOC, but which is pulled in from a link in one of the topics.

       

      If you still get the error, create two copies of your problem toc. Delete half the topics from one, and the other half from the second. Generate each to see if one generates and one fails. (Hopefully one works and one fails.) Repeat the delete/generate steps with the failed half until you can determine the topic causing the issue.

      J
      Jess BlakeAuthorCorrect answer
      Participant
      January 18, 2024

      Thanks, but I ended up finding the solution. In a couple of my topics's source code, some lines had both inline style and a css class. When I removed the inline style, it generated without error. 

        A
        Community Expert
        AmebrCommunity Expert
        Community Expert
        January 17, 2024

        You say that you have two different presets generating to the same folder. I would make sure they are generating to different folders to start with.

        J
        Jess BlakeAuthor
        Participant
        January 17, 2024

        I've tried different folders as well, but I have the same error. I should note that the PDF version outputs completely fine with no errors. 

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