Known Participant

Question

Long path makes PDF corrupted

Forum|Forum|5 years ago
March 23, 2020
1 reply
940 views

Hello,

I am having this problem for the first time. Some PDF files are becoming corrupted, apparently, due to the length of the path. I am wondering why this is happening.

Here is the path:

C:\DATA\OneDrive - XXXX - XXXXXXXXX - XXXXXX XXXXXXXXXX, XXXXXXXXXX Lda\02 PROJ\2002 XXXa\XXXXXXXXXX XXXXXXXXX\200323 XXX XXXXXXXXXX Docs XXXXXXXXXXXXX XXXXXX XXXXXX\10. XXXXXXXXX XXXXXXX XXXXXXXXXXX - XXXXXXXXXX\XX.XX.XX.XX.XXX-XX - XXXXXXXXXXXXXXXXXX_XXXXXX.pdf

I normally try to keep things shorter but after the "200323" it is a tree imposed by the submittal procedure from the client.

A noticeable change has been that since my last installation the One Drive folder picks up the full name of the company when creating the local directory.

Still this is a big problem and other files open from that location. PhotoShop for instance opens the file from that location. Only PDF not.

We have Acrobat Pro and are using it.

The file has been created on a shorter path and opens.

When we move it to the (longer path) folder for submission, it does not open.

When we move it back to a shorter path, it opens again.

When we upload from the longer path to a cloud based sharing platform, it does not open on the other side even with shorter paths.

The obvious solution is upload it from a shorter path. That will solve our immediate problem of fulfilling our submission. But it does not solve the archiving aspect and the accessibility of the files.

Any ideas?

This topic has been closed for replies.

ls_rbls

Community Expert

Hi,

See if adding the long path to the trusted Internet Zones in the Adobe Acrobat Preferences settings works.

You have to do this under Trust Manager settings.

Also, if this is occuring in a DFS replication server environment, consider the win32 API has a limitation to 260 characters only.

Long folder or directory paths, such as in your case, are not supported in this type of environment according to Microsoft guidance.

N

nsgmaAuthor

Known Participant

Thank you ls_rbls

I'll check the Trust Manager.

The strange thing is that this only happens to PDF.

Photoshop and Word documents do open. I cannot change their names unless I go below the limit, but still they open with the original long name.

PDF simply says it cannot open.

The second strange thing is that if I move the PDF to a shorter path, the file opens. However, if I upload it to a cloud from the longer path, it permanently corrupts the file.

So as much as there is a Windows limit to the path length, PDF reacts very different from the other file types, even other Adobe file types.

Anyideas why?

ls_rbls

Community Expert

Hi,

First off, I have to clarify that in my reply above the Preferences settings are in Trust Manager and more particularily in Security Enhanced.

It is under Security Enhanced that you can trust sites from your Windows security zones.

However, A few months ago I was reading about this in other threads.

It seems to be a few things, not just one particular issue.

The one main issue seems to be directly related to Adobe Acrobat still is a 32bit apolication; while most other Adobe applications, like i.e Photoshop, can be installed in a 64bit OS directly as an 64bit app, the same seems not to be the case with Acrobat.

Even though, the 32bit Acrobat application is tested to run in 64bit OS's it seems like there is a direct relationship with how the 32bit security sandboxing, the Enhanced Protected Mode, and how Trust Management settings are affected in a DFS environment.

What some IT Managers have worked around is to turn off Protected View and/or disable Enhanced Security as a work around.

But then, if disabling these layers of security temporarily resolves the issue, you end up with no security enforced at all.

That is the gamble.

Quite a fee users have addressed this to Adobe using the feature request/report a bug wishform.

In my non-developer opinion, this seems to be a bug that has not been addressed in any update since 2015 (and maybe even earlier than that).

See for yourself, don't take my word for it. Try disabling Protected Mode and Enhanced Security, if it works, that is enough indication that the very strong Adobe 32bit security is simply not compatible with a 64bit operating system and therefore has to be disabled.

If you disable Protected View and Enanced Security, and you still get the same problem (even if you run Acrobat with an administrator profile account), then I really lack anymore guessings

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded