Skip to main content
Participant
July 7, 2020
Question

Word 2019 print to PDF Stopped Working

  • July 7, 2020
  • 3 replies
  • 4498 views

Hi, today my Word 2019 print to PDF stopped working.  I have Adobe Acrobat Pro 2017 and I uninstalled and reinstalled it and still does not work.  I also tried running the repair feature in Office and still won't work.  In an attempt to work around this, I tried to select "Microsoft Print to PDF" as a printer but it also does not work.  Much appreciate assistance with this.  Here is the error message that I receive: 

%%[ Error: syntaxerror; OffendingCommand: --nostringval-- ]%%

Stack:
/buildcrdname

%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%

This topic has been closed for replies.

3 replies

Participant
September 26, 2020

Did you ever figure this out?  With Adobe, many times when you see the postscript error, to get around it you'll need go to the Adobe PDF printer preferences, and in the settings, uncheck the box for "Rely on system fonts only; do not use document fonts"

Astonished_worker5E5C
Participant
September 3, 2021

This worked for me! Thank you!

AkanchhaS8194121
Legend
July 7, 2020

Hey there,

 

Looking at the description given above, it seems that you have been trying to convert a word document to .pdf using "Print to PDF" function of MS Office. Did I get this correct?

 

"Print to PDF" is a Microsoft's inbuilt feature of converting word document to PDF. It has its own mechanism of conversion and we don't have a hold on it.

Try File>Print>Adobe PDF or Open Acrobat 2017>Tools>Create PDFs>select the word file and see if that's working.

There seems to be some issue with MS Office, as MS Print to PDF is also not working. In that case we would suggest you to contact to MS support.

 

Thanks,

Akanchha

Eric Dumas
Community Expert
Community Expert
July 7, 2020

Hi,

I don't think this is a compatibility issue.

Once you have checked that all application and operating systeme are up to date, you should contact your local tech support. 

Eric Dumas
Community Expert
Community Expert
July 7, 2020

I had similar issues in the past and it took a few restart and updates to get it right again.