Copy link to clipboard
Copied
Double-clicking on the PDF file it creates, I get "There was an error opening this document. This file cannot be found" even after double clicking on the very file that was just created by the latest Adobe Reader CC that I downloaded and installed. My default installation is Adobe Acrobat 9 Pro. Test print files Adobe PDF printer creates can be opened, at least, but have completely screwed up fonts. It just looks like Adobe PDF printing has been completely hosed somehow. I've tried reinstalling Adobe PDF according to Adobe instructions several times but got the same results. My last effort was to update to latest Adobe Reader CC to let it install the Adobe PDF but same result. How do I get Adobe PDF printer to work properly again? I've spent hours on this to no avail. Following Adobe Online Help doesn't work.
I worked directly with @defaultxmo22hw89o9e and I discovered the underlying cause of the problem he was experiencing.
The default settings for the Adobe PDF PostScript printer driver were improperly set to Rely on system fonts only. This setting should always be disabled. And after any Acrobat update, please check the settings again to make sure that the update didn't reset this setting.
Get the Printer Properties of the Adobe PDF PostScript printer driver instance.
Click on the Advance
...Copy link to clipboard
Copied
....I do see a .log file when I try to print to Adobe PDF that indicates failed printing due to it not finding a font:
%%[ ProductName: Distiller ]%%
Calibri-Bold not found, using Courier.
%%[ Error: invalidfont; OffendingCommand: xshow ]%%
Stack:
-dict-
-file-
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
Copy link to clipboard
Copied
Distiller means your're using Acrobat Pro instead of Acrobat Reader. So I moved this thread into the Acrobat forum.
Copy link to clipboard
Copied
I subsequently installed the latest version of Adobe reader CC, to have install the Adobe PDF printer, but nothing changed in printing to PDF from Microsoft 365 Word Enterprise.
Copy link to clipboard
Copied
From tips there, I tried first repairing Acrobat Pro v9 and then, when that did nothing, uninstalled Acrobat Pro v9 and reinstalled it from the original distribution disk. Again, no change in the problem of Adobe PDF printer failing because it can't find the fonts in the Microsoft 365 Word Enterprise from which I was trying to print.
Copy link to clipboard
Copied
With further trial and error (mostly error), I discovered that, even though selecting Adobe PDF fails with the above font problems, if I choose instead, "Export" and then ""Create PDF/XPS Document", that SUCCESSFULLY creates the PDF version of the document!! At least I now have a work around, although obviously something is still badly wrong with Adobe PDF.
Copy link to clipboard
Copied
One should never have parallel installations of Adobe Acrobat Reader and Adobe Acrobat Pro (or Standard) of either the same or different versions on the same system.
And no, installing Adobe Acrobat Reader doesn't include the Adobe PDF PostScript printer driver instance.
Copy link to clipboard
Copied
I will contact you offline to discuss this issue.
Copy link to clipboard
Copied
I worked directly with @defaultxmo22hw89o9e and I discovered the underlying cause of the problem he was experiencing.
The default settings for the Adobe PDF PostScript printer driver were improperly set to Rely on system fonts only. This setting should always be disabled. And after any Acrobat update, please check the settings again to make sure that the update didn't reset this setting.
Get the Printer Properties of the Adobe PDF PostScript printer driver instance.
Click on the Advanced tab and then on the Printing Defaults button.
Click on the Adobe PDF Settings tab and then deselect the option reading Rely on system fonts only. Then click on Apply. Then click on Apply (if not grayed out) and then OK on the original Adobe PDF Properties dialog.
This fixed the problem.
And again, after any Acrobat updates, check that this option hasn't been re-enabled!