Save as PDF - fail

[Adam – CMENG]

Hello,

I have the problem with saving as PDF.

When I save the opened document to the PDF for the first time everything works.

When I try to save the opened document to the PDF for the second time, I get this message.

At this moment I have only this crazy solution: to close Adobe Framemaker, to open again and save again).

Reinstalling of Framemaker didn´t help..

I am using this Settings.sts https://1drv.ms/u/s!AmJ2x72bqA9dhSo6X2FOm20xBM18?e=gxgJfY

Thanks for advices

Adam

[Jeff_Coatsworth]

What exact version of FM are you using? I take it you're using Save As PDF? Have you tried Publishing as PDF or print to the Adobe PDF printer instance?

[Adam – CMENG]

I am using version 17.0.2 .

If I do it via Publishing it works correctly even if I repeat.

But if I do Save as PDF and then try to publish I get this message:

So Publishing works repeatedly but not Saving as PDF.

I need to work it correctly...

[Jeff_Coatsworth]

Save As and Publish to PDF both use the same mechanism now in FM2022, so I would expect them both to exhibit the same issue - that they don't is curious. Have you checked the log file to see what's going on? Do you have any Console message appearing as it's running? Did you make any changes to the default settings file? 

[Adam – CMENG]

Yes I did changes in deafault settings (is there somewhere in framemaker system folders the default .sts?)

I have this in console:

Log:

When I click on Log, anything opens.

[Jeff_Coatsworth · Accepted solution]

Does that location exist? Do you have full rights to it?

[Adam – CMENG]

Now I have removed current .sts and FM went back to default.

Now it works properly....but still don´t know where the problem was.

"C:\Program Files\Adobe\Adobe FrameMaker 2022\fminit\Publisher\Default.sts"

[Jeff_Coatsworth]

What did you change in the settings? You could try one thing at a time to see what's throwing it off.

[Winfried Reng]

The STS file is just a zip file. You can change the file name extension to zip and then check what is different to the default.

[Adam – CMENG]

There problem was in the path to .sts file. Previously it was placed in folder named with diacritics.

So this is the main problem. It hasn´t affected Publishing but only Saving as PDF.

[mk-will]

Hi, @Jeff_Coatsworth ,

I think even in FM 17.0.2 the "Save as PDF" relies on the old PS-to-PDF route.

I made a test, renamed the AcroDist.exe and then tried to use "Save as PDF" to make a PDF.

When I tried I got an error message, stating (analogues) "The Distiller printer instance isn't accessible."

After renaming the AcroDist back, the "Save as PDF" worked again.

Regards

Stephan

[Jeff_Coatsworth]

@mk-will according to @Winfried Reng it now relies on the Publish route (not exactly sure how, but the fact that the OP found that a bad path was causing all the issues with it, indicates that it's tied in somehow).

[mk-will]

@Jeff_Coatsworth you're right.

So I repeated my test and after renaming the acrodist.exe I tried to make a PDF via the publish route.

And I got the same error message about the missing acrobat distiller printer instance.

As one can decide to use the Distiller even with the publish route FM is making sure to have access to the Distiller even it will not used this time.

My idea about the testing case wasn't well thoght-out.

Regards

Stephan

[Winfried Reng]

Hi Adam, what is in the log file?

Generally Save as PDF works very reliably.There shouldn't be any difference to the Publish pod.

Had this worked before?

Do you have your issue only with specific files?

Had you restarted Windows or FrameMaker?

Best regards, Winfried

[Adam – CMENG]

I think that it worked before I did changes to .sts file. But I am not able to find the default one now.

When the Saving as PDF give the the error, neihter publushing works.

When only doing publushing repeatedly, there is nor error.

Nothing helps.

[mk-will]

As the solution seems to be found my posting isn't relevant anymore.

Hi, Adam ( @Adam – CMENG  ),

you have installed Adobe Acrobat, Distiller and the "Adobe PDF" printer?

Maybe your problem is in the settings of the Adobe PDF printer.

You can make a test: Open a FM-doc and then go to "Print...", change the printer to "Adobe PDF" and print.

Does that work?

Or do you get an error-message?

Regards

Stephan

[Adam – CMENG · Accepted solution]

This method with printing to Adobe PDF is OK.

Problem is solved now. The problem was in folder name with diacritics.