Skip to main content
July 16, 2008
Question

Can't create pdfs

  • July 16, 2008
  • 27 replies
  • 3695 views
Can’t batch or generate either .pdf files singly from RoboHelp 7. Says
“Internal error encountered, Failed to generate Printed Documentation.” This message is not only poorly punctuated, but also not very helpful.

Created Doc (horribly), not the pdf
This topic has been closed for replies.

27 replies

Peter Grainge
Community Expert
Community Expert
September 26, 2008
I doubt it. I had Primo on a machine that worked fine from RH to generate a PDF and I don't have it on a machine that will not generate a PDF direct from RH. The Acrobat team at Adobe have been alerted to the fact that some RH users cannot generate to PDF from RH and have to go via Word first. I am told they will be fixing it but I don't know when.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
September 26, 2008
before I got RH, I downloaded Primo PDF, which is free, cheap, easy and works.

Could Primo somehow be preventing RH from creating pdfs?
August 5, 2008
Morning! Welcome to one of my monir RH headaches:

Failed to print to Test folder in root C drive: same errors. Found the dll with Explorer Search, which is how I knew the proper name for the sub folder was Acrobat 8.0. I found only one PDFmOfficeAddin dll file.
Peter Grainge
Community Expert
Community Expert
August 5, 2008
Go for Leon's suggestion first. If no change, then search your hard disk to see if there are any other instances of PDFMOfficeAddin.dll.

Please post back the result.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Peter Grainge
Community Expert
Community Expert
August 4, 2008
OK. I will let Adobe know that hasn't worked for you either.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
MergeThis
Inspiring
August 5, 2008
Would you want to try reducing the length of the target location? It's currently 134 characters long. Yikes!

Try something like C:\PDFS\Test_UG.pdf.


Good luck,
Leon
August 4, 2008
On Start | Run, tried:

Tried “regsvr32 /u "C:\Program Files\Adobe\Acrobat 8.0\PDFMaker\Office\PDFMOfficeAddin.dll", both with and without the \u parameter, using the proper name for sub-folder (Acrobat 8.0).

Both succeeded, but generating a .pdf still produced a “Failed the generate PDF file 'C:\Documents and Settings\colin.flood\My Documents\Technical Writer\Help files\ User Guide\!SSL!\Printed_Documentation\ User_Guide.pdf'...
Failed to save 'User_Guide.doc'...
Cleaning up temporary files...” message

Internal error encountered, Failed to generate Printed Documentation.
Peter Grainge
Community Expert
Community Expert
August 1, 2008
The following has been suggested.

Start | Run and then enter

regsvr32 /u "C:\Program Files\Adobe\Acrobat 8\PDFMaker\Office\PDFMOfficeAddin.dll"

I tried that and got error messages.

The next step is to then run

regsvr32 "C:\Program Files\Adobe\Acrobat 8\PDFMaker\Office\PDFMOfficeAddin.dll"

I tried that and the DLL registered.

I then tried to generate a PDF and it still failed but you may have better luck. Please post back.

The above assumes the default install path. If you have installed elsewhere, you will need to amend it.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Peter Grainge
Community Expert
Community Expert
July 31, 2008
The thread already covers that you can generate to Word and then to PDF so you have a workaround.

It also covers that the problem is being looked into.

I have no way of knowing whether and when a patch will be issued.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
July 31, 2008
still getting:

Failed to save 'User_Guide.doc'...
Cleaning up temporary files...

Internal error encountered, Failed to generate Printed Documentation.
Peter Grainge
Community Expert
Community Expert
July 29, 2008
I'm sorry but I have said it before, it is not in my opinion up to Adobe to tell anyone how to use a Microsoft product. Microsoft, as I have said, have for commercial reasons allowed users to use methods that bend the correct way of using Word, via Styles.

My understanding is the FrameMaker is stricter about enforcing such rules and that is perhaps why professional documenters like it but why it is not so easy for average users.

I'm out of here.

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