Hi there,
after installing the actual donation-Version 11.6 on my PowerMac OS11.2.1 (BigSur or Catalina before) I get the error massage:
"The directory "/Volumes/Archiv-4TB/.DocumentRevisions-V100" cannot be opened.
EACCES: Permission denied [opendir]"
OSX security settings for full disk access is set to "allow".
Same problem with the normal (non donation) Version.
Thanks for help!
Error message: can't open "DocumentRevisions-V100"-OSX
- Posts: 4
- Joined: 17 Feb 2021
- Attachments
-
- Bildschirmfoto 2021-02-17 um 12.02.53.jpg (34.67 KiB) Viewed 5205 times
- Posts: 4
- Joined: 17 Feb 2021
Any ideas?
- Posts: 4055
- Joined: 11 Jun 2019
It's a problem with permissions on Mac, that folder must have been updated to have different permissions
viewtopic.php?t=7842
viewtopic.php?t=7882
viewtopic.php?t=7842
viewtopic.php?t=7882
- Posts: 4
- Joined: 17 Feb 2021
I have solved the problem. Apparently the data structure of the hard disk was damaged. Hard disk utility repair not possible. I reformatted the hard disk and restored the backup. Now everything works again. Thanks for your help xCSxXenon!
- Posts: 4
- Joined: 17 Feb 2021
Arrgh. The problem occurs again.
But I solved it now (hopefully):
The file: "DocumentRevisions-V100" is not copied by FFS and is excluded by default in the exclude filter:
"*/._**/.DocumentRevisions-V100/"
But either after updating to Big-Sur or to the FFS purchased version (I did both at the same time), this path seems no longer correct.
After I excluded the file in the filter as follows, everything now works without a hitch:
/.DocumentRevisions-V100/
(Without ""*/._** ….“)
I'm just surprised that I'm obviously (almost) the only one with this problem ...
If not I hope this will help.
But I solved it now (hopefully):
The file: "DocumentRevisions-V100" is not copied by FFS and is excluded by default in the exclude filter:
"*/._**/.DocumentRevisions-V100/"
But either after updating to Big-Sur or to the FFS purchased version (I did both at the same time), this path seems no longer correct.
After I excluded the file in the filter as follows, everything now works without a hitch:
/.DocumentRevisions-V100/
(Without ""*/._** ….“)
I'm just surprised that I'm obviously (almost) the only one with this problem ...
If not I hope this will help.
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
Indeed the default filter was broken: There was a newline missing between */._* and */.DocumentRevisions-V100/
- Posts: 8
- Joined: 16 Oct 2014
Dear Zenju, can the default exclude filter be changed? How? Or do I have to correct the exclude filter for all my already defined and future configurations manually? Will the problem be solved with the next software update?
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
Yes, this is fixed in the next update. Until then you can correct the filter manually.
- Posts: 8
- Joined: 16 Oct 2014
Thank you for your prompt reply, dear Zenju!
- Posts: 19
- Joined: 8 Aug 2020
Hello Zenju,
I am seemingly having the same problem with a similar folder, just installed the update 11.1 and still get this message, could you please advise where to get some information to understand how to fix it? I am also running Big Sur in a Mac mini.
Thank you.
Cannot open directory "/Volumes/El 6/.DocumentRevisions-V100/.cs".
I am seemingly having the same problem with a similar folder, just installed the update 11.1 and still get this message, could you please advise where to get some information to understand how to fix it? I am also running Big Sur in a Mac mini.
Thank you.
Cannot open directory "/Volumes/El 6/.DocumentRevisions-V100/.cs".
- Posts: 4055
- Joined: 11 Jun 2019
you can correct the filter manually.
There was a newline missing between */._* and */.DocumentRevisions-V100/
- Posts: 19
- Joined: 8 Aug 2020
Hello Zenju,
Thank you, please bear with me.
I have this as the line in the Exclude folder:
*/._**/.DocumentRevisions-V100/
as far as I can see it looks just like the one you sent me, should I be modifying it somehow?
Thank you.
Thank you, please bear with me.
I have this as the line in the Exclude folder:
*/._**/.DocumentRevisions-V100/
as far as I can see it looks just like the one you sent me, should I be modifying it somehow?
Thank you.
- Posts: 19
- Joined: 8 Aug 2020
My apologies xCSxXenon, I appreciate your response.