Mac: The document could not be printed. There were no pages selected to print.

[patrickw19783566]

Every other App is able to print.  I've tried uninstalling and reinstalling both the application and print driver.  Out of desperation, I updated the OS, and I still cannot print.

Right now, I'm still receiving the error.  My environment:

MacOS: 10.13.1

Adobe Acrobat Reader DC Continuous Release

Version 2018.011.20036

Architecture: x86_64

Build: 18.11.20038.267465

AGM: 4.30.74

CoolType: 5.14.5

JP2K: 1.2.2.39492

Any thoughts?  Are there logs I can look at or tracing I can enable to identify the point of failure?

Best,

-Pat

[Sepher]

I don't understand this. What does this mean? Reinstall what, and how would one reinstall this program without the "case sensitive APFS"?

-Seph

[jds21]

I had exactly the same issue. However, I prefer to keep the case-sensitive file system because it's useful for my development work. For me, I traced the issue to a single folder name.

Acrobat creates a directory:

/Applications/Adobe\ Acrobat\ Reader\ DC.app/Contents/Resources/Resource/TypeSupport/Unicode/Mappings/mac

but then attempts to access it as "Mac" (i.e. capital 'M' in mac)

Making a sym-link fixed printing from Acrobat DC for me:

cd "/Applications/Adobe Acrobat Reader DC.app/Contents/Resources/Resource/TypeSupport/Unicode/Mappings"
sudo ln -s mac Mac

For the record, I'm using Catalina with a case-sensitive APFS filesystem, and latest Actobat Reader: 

Build: 20.6.20042.371807

[barteksalsa]

April, 2020, the issue persist. My setup: Macos Catalina 10.15.4, case-sensitive apfs, Acrobat Reader 20.006.20042.

Temporary solution:

cd "/Applications/Adobe Acrobat Reader DC.app/Contents/Resources/Resource/TypeSupport/Unicode/Mappings"

sudo ln -s mac Mac

[Anon5FBA]

The link solved the problem for me. I wonder how you found out about the issue with the case sensitive file system.

[Spangen]

This problem has been affecting me for literally _years_!

Thank you so much!

[phoenixrichard]

This is brilliant! I have been unable to find a solution to the problem outlined in this thread, and I followed your sym-link fix and it worked beautifully!

[Guest]

Thanks for doing the leg-work on this one jds21, I'd just installed Acrobat after working through a form which de-facto required it to be installed (due to tool-tips being always displayed on Preview, overlaying important fields etc), so I was already frustrated and if this gem hadn't fixed this issue for me I would probably have lost my mind.

[Carlos281950681wo1]

Hi guys, i had this problem, using MacOs Ventura 13.2, tô solve this, the Path where the simlink must be created is: /Applications/Adobe Acrobat Reader DC.app/Contents/Resources/Resource/TypeSupport/Unicode/Mappings. Making the simlink Mac to the mac Folder solve this. 

To solte, open Terminal, an paste this:

cd "Applications/Adobe Acrobat Reader DC.app/Contents/Resources/Resource/TypeSupport/Unicode/Mappings"

sudo ln -s Mac Mac

Just press Retun and type your password.

Problem solved.

Thanks to all.

Sorry my english.

[C5E48]

This is the correct solution. It works on my Catalina APFS case-sensitive system.

Thank you jds21.

[Simon5C53]

I only registered at Adobe to leave a like for this hint. I am also on case-sensitive file system for the same reasons. Adding the symbolic link fixed the issue immediately!

Thank you so much.

[default380lqavmvp2d]

Could someone give a step-by-step for this fix for those of us who never use TERMINAL?  Many thanks.  

[Simon5C53]

Please check the post from @jds21 on the first page of the Thread. You open the App Terminal. 

copy the following and paste it into the Terminal. Hit Enter

cd "/Applications/Adobe Acrobat Reader DC.app/Contents/Resources/Resource/TypeSupport/Unicode/Mappings"

then copy the following and paste it into the Terminal as well. Hit Enter afterwards.

sudo ln -s mac Mac

That should fix the issue immediately (if you happen to have a case-sensitive file system as we do)

[AdDesigner]

SO if that sudo command didn't work for us, how to backtrack/back out of it? undo it? return to original directory?

[Simon5C53]

There is no reason to be concerned about "that sudo command" - What it does is very simple: Currently there is an existing folder called "mac" and on case-sensitive file systems that is a different location than if the folder was called "Mac".

Apparently there is something in the Application that uses a a hardcoded path to a folder called "Mac" although in reality it's called "mac" - on 99% of installations that's no problem because the default file system doesn't care about the difference.

The ln command simply created a link from "Mac" to "mac" - so that whatever reference is used it will find the target. It certainly does no harm to your system and doesn't need to be reverted.

[practical_listener5C1A]

Wow this worked. Crazy. I hope it didn't screw something else up...

[5ilverOrange]

I tried this (but manually changed the file directory rather than via Terminal) and still am getting the same error 😕

Running Monterey 12.2.1 on an M1 Max MBP

[bkcjr]

Hi y'all, 

just to let you know that THIS SOLUTION worked for me pretty well. Here with Monterrey 12.0.1

Thank you so much jds21

[defaultu89d0z97b8jw]

Wow, this worked perfectly. I just had to uppercase that "M" on Mac. I have been having issues as well with Steam for Mac as well I wonder if I can use this method. It is that case senstive issues as well I think. Thank you so much.

[a.hortin]

Just updated to latest version of macOS Monterey (v12.3.1) last night and had this issue today, with not being able to print a PDF. Worked fine with previous Monterey version (v12.2.1). The sym-link fix from @jds21 fixed the issue. Huge props good sir! 🙏

[Tom2546262454zg]

So, here we are in July 2022, and this is still a problem. The fix above worked. C'mon, Adobe. Get with the program.

[Trevor28957380aj1m]

THANK YOU!

I've been cursing this bug and using workarounds since at least 2018.  FIXED!

I created an Adobe account just to thank you for finding their bug.

[enlilragas]

Hello, I've tried the symlink fix and it's currently not working. Does anyone know a new solution?

My current versions are below. Thank you. 

MacOS Version: 14.0 Beta (23A5301h)

[Orion32336023y0yk]

dear goodness,

here it is THREE YEARS AFTER THE FIX IS POSTED TO YOUR WEBSITE, ADOBE,

and this bug is still present.

Props for discovering this.

[Meenakshi Negi]

Hi Orion32336023y0yk,

Thank you for reaching out, and sorry to hear that the issue still occurs.

Please let us know if you get the error on a particular file or all. Did you start experiencing the issue recently?

Share the Acrobat and OS version currently in use. Share the steps and the file so we can investigate this further.

Please also collect the process logs using the steps mentioned here: https://www.adobe.com/devnet-docs/acrobatetk/tools/Labs/acromonitor.html, and share them with us.

Thanks,

Meenakshi

[Michael-M...]

I am having the same problem. Our department is paying Adobe and Microsoft loads of money. For this we get defect products without even support. Adobe says, I should get in touch with our admins. Our IT-Admins only use Windows and "cannot reproduce the problem". This is really rididulous. Adobe's Software products don't work as intended and lack basic functionality.

I am forced to sign and print a non-exportable PDF form from my workplace. Due to Acrobat-Security-Restricutions, I am not able to export, remove security or do anything else with this PDF. I cannot print it from Adobe, as Adobe CANNOT PRINT ON A MAC in 2023, problem knowns since 2018. 

You want to know my workaround? I'm making screenshots just to print those from preview.

This is really riduiculous...