Acrobat pdf maker: The path of document being processed is too long.

You can try using a tool like LongPathTool. It helps manage and delete files or folders with long path issues easily.

I use OneDrive for work and am having this issue. I have tried everyone's suggestions below but still no luck.

Anything that I can do?

++ UPDATE !!

I must say again, that this issue is not related to Adobe Acrobat at all and there is no integration issue with the Acrobat PDFMaker COM Add-in that is shipped with Microsoft Word (in Office365).

The issue (depending on the point of view) is related exclusively between OneDrive and the Microsoft Windows operating system.

After much testing and researching patiently, I was able to find official Microsoft OneDrive guidance to resolve this issue.

It all points to how the OneDrive service syncs your account credentials accross all devices from Microsoft Windows; this applies to both of OneDrive's personal accounts and business.

Furthermore, although it is true that directory (or folder) pathnames do enforce a limitation in how many characters be use ( and that they also must be URL encoded), I tested  all available methods in how to convert a Microsoft Word file to a PDF from OneDrive folders to any desired folder locally in my computer successfully.

In the following link below see the sections that talk about syncing or resetting OneDrive:

• https://support.microsoft.com/en-us/office/onedrive-is-stuck-on-processing-changes-b386b813-9b66-4e47-8c4c-2b45533edccd

NOTE: Clearing the cache also worked for me (in the OneDrive app, or also accessed online via web browser)

And in this other link see how to remove all credential on Microsoft Windows via the Credential Manager:

• https://answers.microsoft.com/en-us/msoffice/forum/all/onedrive-long-path-issue/c5681f17-3ed8-4247-82be-bd64f198f0a8

NOTE IN THE SLIDES BELOW THAT I AM USING A 32BIT VERSION OF ACROBAT ON A 64BIT VERSION OF WINDOWS 10 -- I REALLY WANTED TO PUSH THE ENVELOPE

So, below are a set of 7 different slides that I've prepared for you to illustrate doing all sorts of ridiculous things based on all troubleshooting attempts that the users have exhausted. For example, I created in OneDrive's Documents folder up to six subfolders; two of them with extremely long folder names.

In addition, I also used the files that @rosemarystone  shared with us and copied up to 72  of those Microsoft Word documents to my OneDrive without the need to make the filename shorter, nor copying to the desktop and renaming such files before saving them back to the OneDrive cloud space with.

So here we go:

FIRST SLIDE - Note in the More Details pane how long the folder path is. And also note that I kept the original file names even with the  brackets illegal characters as part of the file names (to include excessive blank spaces, dashes and parenthesis)

SECOND SLIDE - USING THE "SAVE AS" OR "DOWNLOAD AS PDF" METHODS, BOTH WORKED GREAT VIA ONEDRIVE THROUGH THE WEB BROWSER 

THIRD SLIDE - IT SHOWS THAT ALSO FROM ADOBE ACROBAT PROGRAM YOU CAN ACCESS THE SAME ONDEDRIVE FOLDERS AND USE THE CREATE PDF TOOL

FOURTH SLIDE - ILLUSTRATES OPENING THE SAMEONEDRIVE FOLDER FROM MICROSOFT WORD365.

NOTE THAT IN ORDER TO REALLY HIT THE DESIRED ONEDRIVE FOLDER YOU MUST USE "BROWSE" FOR YOUR FILE SEARCH

FIFTH SLIDE - THIS POP UP DIALOGUE WINDOW WILL EXECUTE BEFORE YOU HAVE ACCESS TO THE ACROBAT PDFMAKER COM ADD-IN  DUE TO HAVING CLEARED ALL MY ACCOUNTS CREDENTIALS ON WINDOWS  AND RE-SETTING MY SECURITY CREDENTIALS FOR WEB SERVICES.

THIS IS NORMAL 

JUST FILL IN YOUR ACCOUNT INFORMATION AND TICK THE CHECKBOX "LOG ME IN AUTOMATICALLY"

LAST SLIDE - CLICK ON "CREATE PDF" FOLLOWED BY CLICKING ON YES

And there you have it.

This needs to get fixed! Adobe this post is from 2021!

Adboe, please fix this ASAP - a very long-standing request as we see from this thread. Many people use OneDrive and this issue will be affecting lots of people. I cannot be saving to other locations all the time as a work-around to address this major bug.

Hey Gabbi,

Hope you are doing well.

This is a known issue or say feature limitation which has already been reported and in the discussion. 
The feature will be available soon as the dependencies were on Microsoft. Together, we were able to get this feature approved and will be available in near future release/update. 

Will keep you posted as soon as we'll get to hear anything from engineering.  

Thanks,

Akanchha