Unable to Generate PDF's from Robohelp 7.0.2 Webhelp Projects

[Vyradder]

I've recently upgraded to Robohelp 7.0.2 from X5. I've run into a host of problems with the new product. One is that I cannot generate PDF's from Webhelp. It generates a word doc that I assume it would then go on to PDF...but it can't do it:

Saving 'RxInfo_Adminstration_Application.doc'...
Generating 'RxInfo_Adminstration_Application.pdf'...
Failed the generate PDF file 'F:\Doc\DIS\Help\RxInfo 1.2.6\!SSL!\Printed_Documentation\RxInfo_Adminstration_Application.pdf'...
Failed to save 'RxInfo_Adminstration_Application.doc'...
Cleaning up temporary files...

Internal error encountered, Failed to generate Printed Documentation.

Anyone have any ideas why this would occur? I had no issue doing this in X5.

[Peter Grainge]

Welcome to the forum

We can only help you with the ones you post! :-)

This could be one of two things.

F:\ suggests you are generating to a network drive. You must generate locally. It could be that is a partition on your hard disk in which case sounds like you are one of those who have a problem with generating PDFs direct. There is a bug on the Acrobat side and until / unless they fix it, there's nothing you can do.

Using the same project on three PCs, two will generate PDFs, on the third I have to create a Word document and create the PDF from there.

There's information about Using RH7 on my site. Perhaps that will help with the other issues.

[Vyradder]

I moved both the project and the output directory to my local drive and tried to generate the thing....no dice.

I tried using the RoboPDF generator from the resulting Word doc to generate the PDF...it is unable to save the resulting file locally or anywhere else.

Finally, I had to print the thing to the Distiller from Word to get a PDF out of it.

So, you figure this is the Acrobat problem I am having?

[Peter Grainge]

No I don't figure it is an Acrobat problem, that's what Adobe tell me. It occurs when RH talks to Acrobat but the problem is on the Acrobat side.

Everyone else who has had this problem, and remember I am included, has been able to generate the Word document and then PDF from there and save.

Try first with a new project that you create locally. Tell us how that goes.

[Vyradder]

I created a local webhelp project from scratch:

Saving 'Print_Test.doc'...
Generating 'Print_Test.pdf'...
Failed the generate PDF file 'C:\Robohelp Project\Print Test\!SSL!\Printed_Documentation\Print_Test.pdf'...
Failed to save 'Print_Test.doc'...
Cleaning up temporary files...

Internal error encountered, Failed to generate Printed Documentation.

If I open the word document, then use the Save as PDF option...it fails to save this document.

[Peter Grainge]

No No.

Turn off the PDF option. Generate just a Word document. In Word send it to PDF. Can you save that?

If not try a reboot and give it another go, then post back.

[Vyradder]

The word document generates without any issues. I still cannot use the "Save as PDF" feature within word though. It seems to generate the file, but then cannot save it. I can, however, print to Distiller to generate a PDF from that.

Another option, and this may be what you are describing, is to right-click the word file itself and select "Convert to PDF format". When I do this Acrobat says: "you are missing some files for PDFMaker...do you want to run the repair install for Acrobat?" I selected yes...ran that, rebooted, and it asked me the same question the next time I tried it.

One other factor here, and I'm not sure if this makes any difference, is that I'm runing Acrobat 7.1.

[Peter Grainge]

Acrobat 7.1 is compatible.

I generate from Word by simply selecting Adobe PDF from the list of printers. Different versions will show different text.

However, you now have a means of generating your PDF and that will have to be the solution until Adobe issue a patch.

[Vyradder]

Thank you Peter! I apreciate all your help.

[Lem13]

I've encountered this exact issue. Prior to installing Word 2007, I always generated my printed documentation as a pdf to a network drive with no problems. But now I also get the same error messages that Vyradder got. I am using Robohelp 7.0.2 and Adobe 8.1.2. It creates the Word document (.docx) fine, but then I cannot save the Word document as a pdf regardless of which method I use. If I understand correctly, the problem is with Adobe Acrobat and you mentioned that a patch will be issued. Any idea approximately how soon that will be available? What can I do in the meantime? Any help is much appreciated!

[Peter Grainge]

If you have a document open in Word, the problem does not stop you generating a PDF and saving it. You talk of Save As. From Word, select File | Print and you will then be able to generate a PDF, it is not a Save As operation.

I have no idea when it will be fixed.

[echopraxia]

Akshay Madan was kind enough to post an answer to this issue. I didn't see this post, and posted the same question in a different section of the forum. Resolution is just a matter of re-registering a DLL, which is very quick and painless. The details are listed in this thread: http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=449&threadid=1404923

[Vyradder]

The above solution did not work for me. I re-registered the .dll as described, but the same thing still happens.

[Peter Grainge]

Did you reboot first as I suggested in the other thread?

What operating system?

[Vyradder]

Yes, I rebooted. Windows XP. Generated to the local drive. Acrobat 7.1 Professional. Unable to generate PDF.

[Peter Grainge]

Sorry to be pedantic. Was the order...

Rebooted.

Registered the DLL.

Opened RH to generate a PDF.

Also I notice you are using Acrobat 7. Did you check that DLL exists and amend the path to the location for Acrobat 7?

[Vyradder]

No troubles, Peter.

I first determined that that .dll exists for Acrobat 7.1...it does. Then, I re-registered the .dll. Then, I rebooted and tried to generate the PDF from Robohelp. No dice.

[Peter Grainge]

That's not the order that I indicated is essential.

Reboot the PC and make registering the DLL the first thing you do.

You rebooted AFTER registering. At that point you will get a message the DLL has registered but it has not.

[Vyradder]

The essential order didn't work either.

[Peter Grainge]

I'm assuming you got a message confirming the DLL had registered OK.

Also that you have tried more than one project. (I don't expect that to make any difference but has to be tried).

I will report the issue with this version but please also complete a bug report yourself.

http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

[Vyradder]

Yes indeed, I get a message that confirms the registration of the .dll, and I've tried three different local test projects, one of which I created from scratch.

[Peter Grainge]

Sorry. Looks like it is time to report the bug.

[echopraxia]

A slightly more drastic route... but have you tried uninstalling and re-installing Adobe Acrobat? Adobe Acrobat does not like to have more than one installation at a time, so if you have multiple installations, I would suggest removing them (at your own risk, etc. disclaimers here).

[Vyradder]

I do have more than 1 version of Acrobat installed, yes. You'd think if that was a problem, Adobe's installation would remove older installs. It may be a while before I can get back to you about whether uninstalling them all and reinstalling fixes the problem though because it's a nightmare trying to get Tech Services to push installations up to our local machines. They don't really like us tinkering like this, in general. After spending a week or two getting Framemaker and Robohelp working again, I'm a bit loathe to start messing around to fix a non-critical issue. However, I can likely make this into a business case to get the latest version of Acrobat...I'll let you know how that goes.

[Peter Grainge]

Vyradder

Please test this so that we can determine if the issue is with RH or Acrobat.

Create or locate a Word document in Windows Explorer.

Right click and select Convert to PDF.

If it works, then this is a RH problem.

If it does not work, it is an Acrobat problem.

If RH, then post back here.

If it is an Acrobat issue, you will need to hop over to their forum.