Skip to main content
Participant
January 10, 2023
Answered

RoboHelp stalls when linking/importing FrameMaker files

  • January 10, 2023
  • 2 replies
  • 226 views

I'm having a similar issue. When I link or even try to just import a FrameMaker book, RoboHelp opens FrameMaker, then it opens the book, then it creates the html. That's all great, but the generated html is stuck in the user\appdata\temp\RHTMP folder. The files are there, everything is correct, it just can't seem to get the files from the temp directory to the project folder. Any ideas as to why? 

    This topic has been closed for replies.
    Correct answer Dean26945465p295

    I am using the most up to date versions of both. FrameMaker is 17.0.1.305 and RBH is 2022.0.346.

    The issue turns out to be the location of the source files for the project. On two different systems, the files were unable to be written to the drive, but the drive was a USB external drive. Changing the project to the Documents folder on the C: drive and moving the source files to be imported onto a separate internal drive solves the issue. This is the only issue I've ever had writing to this drive. The Publish window in FrameMaker sets the output directory to the temp directory, then the files just sat there.

    2 replies

    Jeff_Coatsworth
    Community Expert
    Community Expert
    January 12, 2023

    Ok, now that I've moved you into your own thread, let's start with some details - what versions of RH and FM are you running? Are you all patched up? Where are files located; local or on a network drive? Has this worked before or is this the first time trying it?

    Dean26945465p295AuthorCorrect answer
    Participant
    January 13, 2023

    I am using the most up to date versions of both. FrameMaker is 17.0.1.305 and RBH is 2022.0.346.

    The issue turns out to be the location of the source files for the project. On two different systems, the files were unable to be written to the drive, but the drive was a USB external drive. Changing the project to the Documents folder on the C: drive and moving the source files to be imported onto a separate internal drive solves the issue. This is the only issue I've ever had writing to this drive. The Publish window in FrameMaker sets the output directory to the temp directory, then the files just sat there.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    January 13, 2023

    Good to know that you were able to figure it out. Because I discovered there seems to be an internal path length limit to create good hyperlinks in RH from the FM xrefs, I've gone to trying to keep my project lengths to the minimum e.g. C:\projects\<project_name>\ for the RH project.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    January 11, 2023

    @Dean26945465p295 you are probably using a newer version of FM & RH, correct? If so, let's move your question into its own thread instead of tagging along on this older one.

    Participant
    January 12, 2023
    Thanks for all the help Jeff.