2020 Organizers Printed to PDF

[Adam R]

After I installed the newest update "fixing" the organizers, I am having issues with the pdf versions of the organizers. If I print it to paper, it prints fine. If I print it to a pdf and open the pdf in Adobe (XI, 2020, or DC), all of the pages with prior year amounts (W-2s, Int, etc) wont show and come up with an error of "There was an error processing a page. There was a problem reading this document (18).". The pdfs will open fine using Chrome.

Has anyone else had similar issues or know how to fix this? It was working fine when I was doing them this morning before the update.

[clmcpa]

We are also looking for a solution to this issue.  Its the third year of errors in the pdf versions of the organizer.  Not all organizers produce the error, and if you open the pdf and then choose save as "optimized" the new pdf is fine.  The pdf is also fine in any "reader" that does not allow editing of text.  The error is only with Adobe.  Does anyone have a fix?  Lacerte says its an Adobe issue and Adode says its a Lacerte issue, using an invalid font in the organizer (and of course, the user can't control the font used on the organizer).

[Adam R]

I ended up getting it to work from some computers, but not mine. So, I have to print the organizers from a different computer. I have no idea what was different in the settings or what prints, but it works. I had the same problem and had to do the same thing with the 2022 organizers.

[clmcpa]

Do the different computers have different versions of Adobe?

Its and issue on all our workstations.  Some of the orgs are fine and others are not, so we were thinking it was a lacerte thing but haven't been able to find a consistent pattern.  

[Adam R]

My computer, that doesn't work, has Acrobat 2020. The computer it works on has Acrobat XI.

[tonycpa1]

what is the message?

[clmcpa]

The error message:  "There was an error processing a page.  There was a problem reading this document (14).

[George4Tacks]

Lacerte prints using it's own PDF printer. Try the new Lacerte Tool Hub https://proconnect.intuit.com/community/help-articles/help/fix-common-problems-and-errors-with-the-l... and fix the PDF Printer

[clmcpa]

I downloaded the latest version of the tools hub and ran the pdf printer fix program.  Still doesn't work.

[ca-torrance]

Hi.. I have the same issue. "The Document could not be saved. Bad font object or font descriptor" is the error - all our machines have Acrobat Pro (latest version). Its super frustrating.. have re-installed Lacerte, run the PDF Repair tool in the hub and still no luck. Other PDF's are fine. This only happens with Lacerte created PDF files. Commenting so I can keep visibility in the event Intuit or someone in this forum comes up with a fix. 

[sjrcpa]

Having the newest version of Acrobat Pro may be the "problem"

Lacerte probably hasn't been updated for that. They are not cutting edge. For years you had to have Internet Explorer installed even after it sunset.

[ca-torrance]

Thanks.. I was afraid of that as well. I am working now to see if this is happening firm wide. Right now, I have two users with the issue. Both are on the same Adobe version.. so that actually is starting to sound more like the culprit. Thanks for your reply. I am going to see if I can downgrade those versions of Adobe

[ca-torrance]

update: Confirmed its Adobe. Cannot back grade either.. so testing alternate PDF products. Any station we have Adobe has the issue. Foxit handled it no problem... so definitely software related. 

[M1ndH4ck443]

this is a lacerte pdf generator issue.

this is the same thing with quickbooks payroll report export to excel where they blame microsoft as to why the pivots table aren't working.

intuit devs, you are the one's generating the files. you need to follow the requirements to generate the file properly so we can open it without errors.

please fix investigate and fix the issue. just because it opens on third party pdf viewer doesn't mean it's an adobe issue.

https://community.adobe.com/t5/acrobat-reader-discussions/there-was-a-problem-reading-this-document-...