Access denied when trying to open PDFs with Adobe Acrobat (Desktop-App: 1.4.6)


#1

Hey there,

since I updated to latest Cryptomator version 1.4.6 trying to open PDF files with Adobe Acrobat Reader leads to an error:

which is like: “An error occured while trying to open the document. Access denied.” With other applications (Microsoft Edge) I am able to open PDF files in the vault. Futhermore opening PDF files wich are not stored in the vault works fine, also with Acrobat. Does anybody have any idea how to fix this?
Reinstalling Acrobat did not help.

greetings


#2

For me everything work as expected with adobe acrobat reader dc.

How are you opening the document? From the explorer? From the welcome panel of the program?
What happens if you open the document from inside the program over the “open” dialogue? (In the upper left corner, click on file and then the first entry of the popup menu)

Maybe the file is write protected: Windows: How to remove write protection from a file inside a vault


#3

Probably the same incident as me Cryptomator corrupted my files
The user most probably been using the application for sometime.
I doubt it would always be write protected

Update : It was indeed write protected , but why ? How come that is happening ?


#4

Just tested some things, it does not mattter how I try to open files. Both, explorer and open dialogue are leading to the reportet error. Files are not write protected.

Some further information:
-OS: Windows 10
-Interface: Dokany

Switching the interface to WebDAV solved the problem. This is a workauround I can accept but it does not solve the real porblem so I am still looking for further ideas.


#5

Hi

I am experiencing exactly same issue from today suddenly.
I am using Windows 10
Cryptomato 1.4.6 (Dokany)
and I can open XLS file for instance but no PDF.
Thanks for your help

After re-reading the posts, I cahnged the mounting method to webdav and I can now open the PDF files.
Don’t know much about the difference btw Dokany vs WebDav. But I confirm when switching to dokany it’s not worling


#6

Hi All,

I’m using 1.4.6 on a Windows 10 x64 machine too.

I see the same thing too. I never had this problem before but I recently installed and switched to using dokany vs WebDAV.

I thought dokany would be better (cleaner) but if I’m going to see issues like this, why would I use dokany?

I need this to be bulletproof.

Thanks


#8

Hi everybody,

Good to hear I’m not the only one affected.
Running Cryptomator v1.4.6 on a Win 10(E) x64 machine and only recently started to get problems.

First, I didn’t or doesn’t accept the correct password (on a Dropbox directory). Have to pause and reactivate Dropbox sync before Cryptomator opens the directory.

Then, PDFs cannot be opened (“Access denied” or “General failure” in Acrobat, “A device attached to the system is not functioning” in PDF X-Change Viewer). If I delete the same files, they disappear until I refresh the directory, where they appear again… Edge also doesn’t want to open the PDF.

Switch from Dokany to WebDAV didn’t help anything. Any suggestions?

Regards


#9

@als If the files are not deletable, they are read-only. See here: Careful with files with read-only attribute


#10

Can anybody create a debug log and send it to me via PM? It could be helpful since i can’t reproduce the issue and maybe the log file contains a hint.


#11

Thanks, @infeo. That was in fact the case. No idea, though, how those files in the file system came to be “protected”. You find my debug log dump under https://github.com/cryptomator/cryptomator/issues/864.


#12

Cool that this is solved. Regarding the log-file, i meant getting an insight of the problem where the vault is not write protected but .pdf files not accessible.:wink:


#13

Hi,

I’m experiencing the access denied errors when opening PDFs from the encrypted drive, too.
Using Cryptomator 1.4.8 + Dokany on Windows 10 x64 Enterprise 1809 17763.437 (on Core i5 + SSD).
Most PDFs open without problems but some random PDFs give an access denied error when opening them in Adobe Reader DC 2019.010.20099.
Retrying these PDFs may result in some more errors until it finally works. So in the end every PDF opens successfully but there seem to be PDFs that are more error prone than others.

I had Cryptomator write a debug log, so I got an error and a following successfull opening of that same PDF in a log.

@infeo Obviously I can’t send you a PM but could eventually reply with the log attached if you send me a PM.

Cheers
Klaus


#14

Very, very strange…

@Klaus_Salger i send you a message, just answer me.


#15

I was experiencing the same issue when opening PDFs in Abode Reader, but the problem didn’t occur when opening the PDFs in Chrome.

I found the following article that shows you how to disable protected mode in Adobe Reader. I know this isn’t a fix, but it’s a workaround for those who don’t mind disabling protected mode.